The dashboard for auto-checkout organizations
Run your ACO like an operation, not a spreadsheet.
ACOMaster gives your ACO one dashboard for the whole job. Customers load themselves in, runners work a single queue, and PAS — Payment After Success — lands on a ledger instead of a DM thread.
Big-box drops. TCG releases. The major retailers your ACO already runs.
The tour
The whole operation, one dashboard.
Four screens carry the day-to-day. They’re shown here exactly as they run, using a made-up ACO and made-up customers.
Bring the fleet you already have.
Import the exact files your bots read today — the same formats out as in, with verified round trips on the interchange formats. Load a customer’s profiles on their behalf before they’ve ever signed in. No hand conversion, no re-typing.
Every customer gets their own dashboard.
Members create, add, or bulk-upload their own checkout profiles, retailer logins, addresses and mailbox — and keep them current without going through you. Sign-in is Discord on your ACO’s own subdomain — if they’re in your Discord server they’re in, with no login passwords to manage. You watch intake fill in from the dashboard and step in on anyone’s behalf when they stall.
Runners get the whole job on one bar.
The queue groups work by customer: tick one box for the whole set, claim in bulk, export profiles and logins in the format the bot wants, and the mailbox panel is one click away when a confirmation code lands. Every reveal is audited — and the customer can see it.
PAS, tracked like money should be.
PAS — Payment After Success — is the deal: your customers pay when a checkout lands. Record what’s owed, submit it once it’s earned, and confirm receipt when the money arrives — with refund offsets kept beside the charge instead of erasing it. Runners can raise and submit; confirming payment is the owner’s alone. ACOMaster tracks PAS; your ACO collects it — the platform never touches the money.
Your brand on the door
Your customers arrive at your front door.
Every ACO gets its own subdomain, name, logo and accent — the dashboard wears them everywhere your members look. The ACO above is one we made up for these screenshots; yours carries your own name and colors.
And the rest of the job
Everything your ACO stops improvising.
Discord-native sign-in
Membership in your server is the key. Roles gate who sees what, and nobody manages login passwords.
Secrets treated like secrets
Sensitive fields are envelope-encrypted at rest. Reveals are purpose-bound, and every one lands in an audit log the customer can read.
Mailbox at hand
Customers connect a mailbox; when a retailer sends a code, the runner working that customer has it one panel away — audited, never silent.
A record of what your bots post
Our Discord bot watches the channels you point it at and keeps a rolling 30-day record of what your checkout bots post there.
Guides built in
Mailbox setup, PAS explained, retailer requirements — the questions your ACO answers weekly, answered once.
Your formats, both directions
Generic CSV, AYCD JSON, Valor, Shikari, Refract — in and out, so your data is never locked in. Running something else? Tell us and we’ll look at adding it.
Your members hear it from the bot
A checkout lands and the bot tells the customer in Discord. PAS comes due and it tells them that too — what they owe, and how to pay it.
How it works
From spreadsheet to operation.
We set your ACO up personally
Your subdomain, your branding, your Discord linked — you don’t configure a platform, you move into one.
Your data comes as it is
Customers self-onboard with Discord, or you import the files you already have on their behalf. Day one is a migration, not a re-type.
The loop runs
Runners work the queue, checkouts land, and PAS — Payment After Success — lands on the ledger with an audit trail behind it.
Trust
Built for the data your ACO is trusted with.
Isolated tenants
Each ACO runs in its own isolated tenant. Your customers, your data, nobody else’s dashboard.
Encrypted at rest
Sensitive fields are envelope-encrypted and masked by default across the dashboard.
Audited reveals
Every reveal is recorded — and shows up in the customer’s own activity log, not just yours.
Never locked in
Your data exports back out in the same formats it came in. Leaving is a download, not a negotiation.
We set your ACO up personally.
Questions ACOs ask
The short answers.
What happens to our Discord server?
Nothing moves. ACOMaster links to the server you already run — sign-in checks membership, roles map to permissions, and the bot only watches the channels you point it at.
What do our customers see?
Their own dashboard on your subdomain: their profiles, logins, addresses, mailbox, activity log and PAS charges — and nothing that belongs to anyone else.
How do we get our data in — and back out?
Both directions, in the formats your bots already use: generic CSV, AYCD JSON, Valor, Shikari and Refract. Import on day one from the files you already have; export the same way any day you like. Running a bot we don’t list yet? Talk to us.
Which retailers?
The major retailers ACOs run today. Running somewhere else? Talk to us — coverage follows the ACOs.
Do our runners see everything?
No. Roles decide what each person can reach: runners work the queue and export what a job needs, management handles people and PAS, and confirming a payment is the owner’s alone. Sensitive fields are revealed on purpose, and every reveal is recorded where the customer can see it.
What does ACOMaster never do?
It doesn’t run checkouts, doesn’t process payments, and never takes custody of PAS. It’s the ops dashboard — not the bot, and not the bank.
What does it cost?
Plans are per-ACO. Tell us about your operation and we’ll set yours up.