Install and authorize ArkMart
- Sign in with Discord and choose a server you can manage.
- Select Invite bot if ArkMart is not online there.
- Keep the requested permissions enabled.
- Place the ArkMart role above seller roles the dashboard must assign.
- Open Operations and run the permission check.
ArkMart needs View Channels, Send Messages, Embed Links, Attach Files, Read Message History, Manage Channels, Manage Roles, Manage Threads, Create Private Threads, and Send Messages in Threads. Administrator is not required. A channel override can still block a permission granted by the server role, which is why the live check tests configured channels.
Configure the shop
- Set the shop name, accent, default currency, and retention in Settings.
- Choose sales, feedback, transcript, ticket log, referral log, and operations channels.
- Enable automatic inventory channels or assign existing channels.
- Open Team & roles, sync Discord, and assign seller roles.
- Connect a broad or granular seller role to the inventory it can fulfill.
Re-running create or repair is idempotent: ArkMart first looks for saved channels and recognizable existing channels. Review the proposed routing before allowing it to create anything new.
Prepare and publish inventory
Inventory is grouped into dinos, resources, boss fights, bases, and custom services. For each listing, set its options, amount, currency, unit, quantity, image, Discord channel, and seller routing. Dino stats use base + mutation; keep every stat for your records and mark only buyer-relevant stats for display.
Premium shops can upload an ArkLines database. Review the species and variant match, focus stats, color schemes, and Discord routing. Tek and X variants are matched automatically where reliable; uncertain matches require confirmation. Select only the reviewed lines and publish them to create or update listings.
Buyer cart and checkout
A buyer chooses a listing option, optionally chooses one of that line's observed color schemes, and adds it to a private cart. Buyer controls change quantities or remove unclaimed items without adding message clutter. Checkout locks in a price snapshot and notifies only relevant seller roles.
The buyer can use /emptycart to remove all remaining unclaimed items or /endsale to release a pending seller fulfillment when the workflow permits it.
Seller claim, delivery, receipt, and feedback
- An eligible seller selects only items they can fulfill.
- They confirm the claim; a private sale area is created for buyer and seller.
- The seller reviews the prefilled completion form and marks the sale complete.
- ArkMart records the sale and presents the buyer with an ephemeral feedback request.
- The completed cart remains for up to four hours for feedback, then closes early after feedback or at the deadline.
Manual sales can be recorded with /registersale. Use a Discord time value accepted by the command and a non-negative amount.
Build ticket panels
Create a panel in the dashboard, add guided questions, choose its destination, staff roles, transcript behavior, and actions, then publish. Buyers open a private ticket; staff can claim, quote, mark delivered, complete, export a transcript, or close it according to their role. Button availability and authorization are both checked server-side.
Run an auditable giveaway
Create the prize, timing, winner count, and eligibility in the dashboard. Entry and claim controls are ephemeral when only one person should see them. Winner selection, rerolls, and claim status are preserved in audit history. Giveaway configuration must never promise paid or manipulated odds.
Operate and troubleshoot
Operations shows bot and worker heartbeats, Discord permission results, pending deliveries, and jobs stopped after a permanent error. Fix the reported channel or role issue before selecting Retry. Dismiss only an obsolete event you intentionally no longer want delivered; dismissal keeps an audit note rather than deleting history.
For help, see Support. Never share a bot token, OAuth secret, SSH key, or production database in Discord.