POS Integrations

POS integrations connect your marketplace to the point-of-sale systems merchants already run — Clover, Square, and Toast are supported. Once an outlet is connected, marketplace orders flow into the merchant’s POS so their staff work from one screen instead of watching a second device. Each integration includes a connection test and a health indicator, so a broken link surfaces to your team instead of silently dropping orders.

Where to find it

In your admin dashboard: browse available integrations at Dashboard → Settings → Integration → Plugin List (/configuration/integrations/integration/plugin-list); manage configured ones at Plugin Config (/configuration/integrations/integration/list). Requires admin access; the connect step needs the merchant’s POS account credentials, so plan it as a joint session with the merchant.

Why it matters for a marketplace

For merchants who live in their POS, “check another tablet for online orders” is the #1 operational objection to joining a marketplace. A POS integration removes it:

• One screen for outlet staff — marketplace orders appear in the POS next to walk-in sales.
• One sales record — the merchant’s end-of-day POS totals include marketplace orders.
• Existing kitchen routing — if the POS drives kitchen printers or displays, your orders ride along.

Orders still appear in the partner app as well — the POS copy is additional, not a replacement, and the order’s lifecycle on the marketplace continues regardless.

Supported systems

POS	Orders sync	Notes
Clover	Yes
Square	Yes	Connects via a secure Square sign-in popup
Toast	Yes

Catalog and price syncing varies by provider — what can be pushed or matched between the marketplace catalog and the POS depends on what each system exposes. Confirm current capabilities for a given provider with your SuperApp account manager before promising a workflow to a merchant.

Connecting a merchant’s POS

1. Open Dashboard → Settings → Integration → Plugin List (/configuration/integrations/integration/plugin-list) and choose the merchant’s POS from the available integrations.
2. Fill in the integration form — a name, the integration type, priority, and any conditions controlling when it applies (e.g. scoping it to the right outlet).
3. Complete the provider-specific connect step. For Square this is an OAuth popup — the merchant logs into their Square account when prompted and authorizes the link. Other providers have their own connect step on the same form.
4. Save, then run the Test Connection action before relying on it during service.

Configured integrations live at Plugin Config (/configuration/integrations/integration/list) for later editing, testing, or disabling.

Finish with a real test order

After Test Connection passes, place one low-value order to the outlet and verify it lands in the POS the way staff expect — items, options, order type. Do this with the merchant on the line; it’s the moment they start trusting the integration.

What stays on the marketplace

The POS shows the order; the marketplace still runs it. Merchant staff should keep doing these in the partner app, not the POS:

• Status updates — accepting, marking ready, completing. Customer notifications fire from marketplace statuses, so updating only the POS leaves customers uninformed.
• Edits and refunds and cancellations — these must happen on the marketplace so payments and notifications stay correct.
• Catalog and availability changes — managed on the marketplace (see Catalog Builder); whether they flow to the POS depends on the provider.

Make this part of the merchant’s training when you switch on their integration — the most common integration complaint is really a workflow misunderstanding.

A per-merchant rollout checklist

• Confirm the merchant’s POS is Clover, Square, or Toast, and which account/location it runs on
• Schedule the connect step with someone who has the merchant’s POS credentials
• Create the integration from Plugin List, scoped to the right outlet via its conditions
• Run Test Connection, then a low-value end-to-end test order
• Walk staff through where marketplace orders appear in their POS — and what still happens in the partner app
• Note the go-live date so health issues can be correlated later

Health monitoring

Each integration has a health indicator so your operations team sees a failing link — expired POS authorization, rejected requests — before merchants notice missing orders. When health flags a problem:

1. Open the integration at Plugin Config.
2. Run Test Connection to confirm.
3. Redo the connect step with the merchant (e.g. a fresh POS sign-in) and re-test.

Build a habit of checking integration health for high-volume merchants as part of routine operations rather than waiting for a complaint.

Troubleshooting

Symptom	Try this
Connection popup blocked or blank	Allow popups for the dashboard; have the merchant confirm they can sign into their POS account directly, then retry
Test Connection fails after working previously	The POS authorization or credentials likely expired — redo the connect step from Plugin Config
Orders not reaching the POS	Check the health indicator and run Test Connection; confirm the integration is enabled and its conditions match the outlet’s orders
Order arrives in the POS but looks wrong	Record exactly what differs (items, prices, options) and contact SuperApp support — provider mapping may need adjustment
Merchant asks about catalog sync	Capabilities differ per provider — verify with your account manager before committing

Related: Live Orders · Receipt Printing · Outlets