How to add online ordering to Toast, Clover, or Square

Adding online ordering to a POS starts with the order paths you need to support. Marketplace orders, orders from a direct storefront, and orders entered by staff may use different connectors. Document each path before choosing a setup.

Separate the two order paths

• Marketplace path: identify every third-party marketplace, the Stream account that manages it, and the POS location that should receive the order.
• Direct-ordering path: identify the storefront, payment flow, menu authority, and connector that will send the order to the POS.
• Do not assume that a connector used for one path also supports the other path or the same data fields.

What Stream documents for Toast, Clover, and Square

Stream's integration directory currently lists Toast, Clover, and Square as POS integrations. Its product page describes publishing one menu to connected third-party providers and sending their orders to the POS. Availability and setup still depend on the selected POS, provider, account, and region.

Conditional connection checklist

1. Confirm the exact POS product, account, location, and software version.
2. List the channels that create orders and decide which system owns the menu for each channel.
3. Ask the connector owner which objects move in each direction: orders, prices, modifiers, availability, inventory, cancellations, refunds, and prep times.
4. Map taxes, tips, service charges, discounts, payment tenders, and fulfillment types before testing.
5. Use the provider's current setup guide for the selected POS instead of copying credentials or steps from another integration.

Verify before going live

• Place a test order for each channel and fulfillment type in a non-production or approved test setup.
• Confirm the order reaches the intended store with the correct items, modifiers, totals, tax, payment status, and customer notes.
• Change a menu item and verify only the directions the provider documents; do not infer two-way sync from one successful order.
• Test rejection, cancellation, unavailable items, duplicate delivery, connector downtime, and retry behavior.
• Record the owner, escalation path, and rollback procedure for every connector.

A successful setup is not 'the POS is connected.' It is a documented order path whose supported data, failure behavior, and operating owner have been verified for the exact account and location.