Ingest and acknowledge marketplace orders via Chowly middleware into a POS
domain: chowly.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Work with Chowly's onboarding team to enable your POS as a supported integration target; Chowly's API is partner-gated and not publicly self-serve.
Configure the POS-side webhook or polling endpoint that Chowly will use to inject normalized orders.
When Chowly delivers an order payload, parse the unified order schema covering items, modifiers, delivery/pickup type, and customer details.
Acknowledge receipt to Chowly within the required window; Chowly handles upstream acknowledgment to the originating marketplace (Uber Eats, DoorDash, etc.).
Map Chowly item IDs to POS menu items using the shared mapping table maintained in the Chowly portal.
For errors (unmapped items, closed store), return the appropriate error code so Chowly can surface a rejection back to the marketplace.
Known gotchas
Chowly normalizes orders from multiple marketplaces into a single schema, but marketplace-specific fields (e.g., tip breakdown, promo codes) may appear in extension properties — do not assume a flat order structure.
Menu mapping must be kept in sync; if you add items to the POS without updating the Chowly mapping, those items will fail to inject and orders may be rejected.
Chowly's direct API access for custom integrations is restricted to vetted partners; independent developers should contact Chowly directly rather than attempting undocumented endpoints.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?