The console is dense because it currently combines merchant setup, support queue work, and platform diagnostics. Use the mode switch first. That reduces the page to the parts that match the job.
Use this when the merchant already has an API key and needs to get from catalog to buyer link quickly.
Use this when support or platform ops need to review inbound work, issue the first key, or validate webhook flow.
Console Session and click Load Console.Catalog Import And SKU Picker.Buyer Link Generator.Open Buyer Checkout or Copy Buyer Handoff.Find Buyer Order.Paste the merchant key and confirm the account snapshot is real before touching catalog or buyer links.
Load Console
Use CSV import and the SKU picker so nobody has to hand-copy raw SKU IDs.
Import Catalog CSV
Create the buyer link and keep the merchant reference for trace and support handoff.
Create Buyer Link
Ops mode.Support Queue and First Key Requests.new, contacted, qualified, closed.First Key Requests when the merchant is ready.Webhook Smoke and inspect deliveries.Start with work intake, not diagnostics. Review current briefs and bootstrap requests first.
Load Support Briefs
Update the workflow state before issuing keys or asking for more data, so the queue stays trustworthy.
contacted / qualified / closed
Use webhook smoke and deliveries after the queue is understood, not as a default first action.
Run Webhook Smoke
Opening the console in All mode and treating every panel as required for every user.
Pick the role first. Merchant mode for setup. Ops mode for queue and diagnostics. All mode only when you explicitly need browser identity or cross-cutting debugging.
Go to /bootstrap, submit the intake, then process it in /bootstrap-intakes.
Go straight to /console, switch to Merchant, and use catalog import plus buyer link generation.