In the Otter portal, navigate to the POS Integration settings and select your POS system (e.g., Toast, Square, Lightspeed) from the supported integrations list.
Authorize the connection by providing the required credentials or completing the OAuth flow for your POS; Otter will validate the connection.
Map your POS menu items to the delivery platform menus managed in Otter, ensuring that item IDs and modifier structures align so orders inject correctly without manual mapping errors.
Configure Otter to auto-accept incoming orders (if supported by your workflow) so that orders from all connected delivery platforms are automatically injected into the POS without requiring tablet interaction.
Place test orders on each connected delivery platform (DoorDash, Uber Eats, etc.) and verify they appear correctly in the POS with items, modifiers, and delivery details intact.
Monitor the Otter dashboard for injection error rates; address any unmapped items that cause order failures before going live.
Known gotchas
Otter's POS integration injects orders into the POS in real time, but the integration depth varies by POS system — some POS integrations receive full orders with modifiers while others may only receive a notification requiring manual entry; confirm the capability level for your specific POS before relying on it for fully automated order flow.
Otter's open API is available for custom integrations, but accessing it requires working with Otter's partnerships team; it is not a fully self-serve public API.
Auto-accept behavior means orders are committed before kitchen staff review them; ensure your menu and hours settings in Otter are accurate to avoid accepting orders for unavailable items or during closed hours.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp