ACO HQCommand CenterControl every checkout from one connected command center.
ACO HQ unifies custom Discord webhook routing, checkout processing, member identity, live drops, orders, PAS, and reporting—so your operation stays fast without becoming scattered.
Pokémon Center Release
Real-time roster and product performance.
Configure the entire Discord checkout pipeline from ACO HQ.
The Webhook Configuration Center acts as the control plane for your relay. Add or disable scraper sources, target exact Discord webhook users, define where success messages should go, test destinations, and inspect every delivery result.
ACO HQ can route matched members to their group destination, unmatched checkouts to a dedicated channel, and use the original environment webhook as a final fallback.
Source→Railway
Relay→Match
Engine→Discord
Destination
More than a webhook relay.
ACO HQ preserves the context behind every checkout and turns it into a complete workflow your team can operate, audit, and improve.
Custom Webhook Control
Configure scraper sources, destination routing, relay health, fallback behavior, test delivery, and audit history without editing the relay.
Member & Profile Identity
Connect multiple checkout profile names to one Discord member while preserving the immutable Discord user ID used for reliable mentions.
Unassigned Operations
Capture unmatched checkouts instead of losing them, route them to a dedicated Discord destination, and assign them to a member later.
Live Drop Zone
Detect drops from incoming activity, create manual drops, manage target rosters, and monitor checkout progress as the release happens.
Checkouts & Orders
Convert successful webhook events into organized checkout and order records with bot, runner, retailer, profile, member, and drop context.
Product-Level PAS
Set PAS by product, track outstanding balances, manage member invoices, verify completion, and maintain payment history.
Briefings & Attention
Surface the newest activity, failed webhooks, missing PAS, unmatched profiles, open drops, and other operational priorities.
Analytics & Flex Images
Review member and bot performance, monitor drop outcomes, and generate branded share images directly from verified drop data.
Built around the work that happens after the webhook.
A successful checkout is only the beginning. ACO HQ keeps member identity, drop progress, order details, and PAS responsibilities connected.
Multiple profiles. One reliable Discord member.
Use the profile name from the incoming checkout as the primary account match while retaining the Discord user ID for dependable mentions.
Track the release while it is happening.
See target progress, successful members, unit counts, product performance, and the newest checkout activity.
Know exactly what is owed and why.
Assign different PAS values by product, group the results into member invoices, and track payment completion.
Start with what needs attention.
ACO HQ surfaces operational priorities before they turn into cleanup work.
From Discord message to audited operation.
Every step is designed to preserve attribution, prevent duplicate work, and keep the next action obvious.
Listen
The Railway relay watches only the Discord servers, channels, and webhook users enabled in ACO HQ.
Validate
The protected ingest endpoint authenticates the relay, detects the program, parses the checkout, and blocks duplicates.
Match
ACO HQ matches the checkout profile to the correct account record, Discord member, member group, product, and drop.
Create
Checkout and order records are created with their full operational context while live drop and dashboard metrics update.
Route
The success notification is delivered to the member group destination or the dedicated unassigned checkout channel.
Audit
Delivery status, destination source, relay activity, webhook payload, and processing results remain visible for review.
Secure by design
Public presentation. Private operations. Protected delivery.
The public homepage is separated from the authenticated workspace. Relay configuration and operational pages remain protected, inbound webhook requests require the shared secret, destination URLs stay masked, and delivery history remains available for review.Operational routes require a valid ACO HQ session.
Relay configuration, status, and ingest calls use the shared webhook secret.
Discord webhook values are not exposed as plain text throughout the interface.
Successes, failures, destination sources, and timestamps remain traceable.
Built for operators who need speed without losing control.
Sign in to manage custom webhook routing, live checkout activity, members, drops, orders, PAS, and reporting from one workspace.