Orders & Logistics

The orders system turns supply requests into a tracked workflow: a member posts what they need, anyone can offer to fulfill it, and the requester confirms delivery while the bot keeps the remaining quantity up to date. There are three flavours:

• Standard orders (/order) — request any item and quantity.
• Wikelo Emporium orders (/wikelo-order) — request every material for a known Wikelo contract in one go.
• Org Funding (/org-funding) — a credits-only collection drive with a live contributor leaderboard, restricted to a designated officer.

Setup (admin)

Enable and point the system at a category before anyone can order.

1. Open the Orders tab in your guild's dashboard, or run /config-orders in Discord.
2. Set the category where the bot will create order channels. This is required — each requester gets their own requests-<username> channel created under it.
3. Toggle Enabled on. Save.

/config-orders options:

| Option | What it does | |---|---| | category (required) | Category under which requests-<username> channels are created | | enabled | Turn the whole orders system on or off | | org_tax_channel | Channel where Org Funding orders are posted | | org_tax_leaderboard_channel | Channel for Org Funding leaderboards (defaults to the order channel) | | org_tax_officer | A single user allowed to start Org Funding orders | | org_tax_officer_role | A role whose members may start Org Funding orders |

Standard orders

1. A member runs /order item:<name> quantity:<n> price:<per-unit> [unit:<SCU|units|…>]. item, quantity, and price are required; unit defaults to units.
2. The bot posts an order embed (item, remaining quantity, price per unit, total potential value) in the requester's requests-<username> channel and pins it. The embed carries Fulfill Order and Delete Order buttons.
3. A fulfiller claims it: anyone clicks Fulfill Order and fills in the modal — the amount they can supply, a pickup location, and optional notes. They can claim a partial amount.
4. The requester reviews the offer: the bot DMs the order's creator an offer card with Accept / Decline buttons. On accept, the fulfiller is notified and the card shows a Confirm Delivery button.
5. Delivery is confirmed: once the goods change hands, the requester clicks Confirm Delivery. The order's remaining quantity drops by the delivered amount and the channel embed updates.
6. Auto-completion: when remaining hits zero the order is marked fulfilled, the embed replies "fully fulfilled", and the message unpins.

The requester or an administrator can click Delete Order at any time to cancel it.

Wikelo Emporium orders

/wikelo-order lets a member request every material a Wikelo contract needs at once, instead of filing each item by hand.

1. The member runs /wikelo-order contract:<name> — the contract field autocompletes from the active contracts the bot knows about.
2. The bot shows a modal asking for the price per unit the member is willing to pay for each required material (up to five per contract).
3. On submit, the bot creates a thread named after the contract inside the requester's requests-<username> channel and posts one standard order per material — each with the contract's required quantity, the price the member entered, and the usual Fulfill / Delete buttons.
4. From there each material order follows the exact same fulfill → accept → confirm-delivery flow as a standard order.

Where contracts come from: the contract catalogue (each contract's name and its list of required materials/quantities) lives in the bot's wikelo_contracts data. It is refreshed automatically by a scheduled crawler job and can be reviewed or edited by an admin under Admin → Wikelo Contracts in the dashboard. Only contracts marked active appear in the /wikelo-order autocomplete.

Org Funding (also called "Org Tax")

Org Funding is a credits-only order that only a designated officer can start. Use it to collect aUEC from members toward a target, with a live leaderboard of who has contributed the most. (The command is /org-funding; the dashboard labels this section Org Tax.)

Setup

1. In the Orders tab (or /config-orders), set under Org Tax:
   • Org Tax Channel — where each funding order and its leaderboard are posted.
   • Officer Role and/or Officer User ID — who may start a funding order. Administrators can always start one.
   • (optional) an Org Tax leaderboard channel via /config-orders org_tax_leaderboard_channel: if you want the leaderboard posted somewhere separate from the order itself; otherwise it posts in the same channel.
2. Save.

Running a drive

1. The officer runs /org-funding create amount:<aUEC> [label:] — e.g. /org-funding create amount:1000000 label:Q2 Operations Funding.
2. The bot posts two messages in the org-funding channel and pins them:
   • an order embed showing target / collected / remaining aUEC, with a Fulfill button;
   • a separate leaderboard embed listing the top 10 contributors.
3. Members click Fulfill and enter the amount of credits they're contributing (no pickup location — it's credits only).
4. The officer (the order's creator) receives a DM and confirms receipt with the action buttons. A contribution only counts toward the total and leaderboard once confirmed.
5. When the collected total reaches the target, the order auto-closes, the embed shows Tax fulfilled ✅, and both messages unpin.

Command reference

| Command | Who | Purpose | |---|---|---| | /order | Members | Request a single item/quantity | | /wikelo-order | Members | Request all materials for a Wikelo contract | | /org-funding create | Officer / Admin | Start a credits funding drive | | /config-orders | Admin | Configure the orders system and Org Funding |

Related

• The Goal Events feature (see the Events guide) reuses the orders pipeline to run timed delivery drives; per-order delivery confirmations feed the goal-event leaderboard.
• See the Tokens & Rewards guide for the voice-participation economy.

Have a question that isn't covered here? Ask in support.