Stream connection planning
This note prepares a project-specific discussion. Ordering.co's public StreamOrders overview says its team sets up the connection and describes menus and orders staying in sync across Stream's delivery channels and an Ordering.co storefront. That statement does not confirm that a connector is deployed or configured for a particular project.
For the integration overview and next step, see Stream on Ordering.co.
Details to bring to the review
Share the information needed to scope the connection:
- The Stream account and restaurant locations involved.
- The point-of-sale system and the Stream channels currently in use.
- Which menus and order flows the project wants reviewed.
- The Ordering.co businesses and storefront scope involved.
These are scoping details, not confirmed compatibility requirements or a supported-product list. Do not include passwords, tokens, or other credentials in a shared request.
Confirm the project-specific connection
The public Ordering.co overview does not specify the supported POS/channel combinations, geographic coverage, precise data direction, synchronization timing, or status of a particular project. The Ordering.co team should confirm those details and the implementation and validation scope before anyone relies on the connection. This note does not describe Dashboard controls, installation steps, endpoints, or credentials.
Use the Stream official website for provider context about Stream's POS and online-channel product. Stream's general capabilities do not prove that a specific combination is supported by Ordering.co.
Request a coordinated scope review
Share the project details with Ordering.co to request a connection review. The team can confirm the applicable project scope and next setup steps.