{"id":"d4dfafc1-05d7-467f-9a2d-66415e76b82d","task":"Map POS products to Flipdish menu entities using metadata and sync menu changes","domain":"developers.flipdish.com","steps":["Retrieve the existing Flipdish menu via GetMenuById to view current sections, items, and option sets","Store your POS product IDs as metadata on each MenuSectionItem/MenuOptionSetItem (or use the PublicId property plus your own mapping table) so order webhooks can be matched back to POS products","Use the create/update menu-entity endpoints (e.g. CreateMenuSectionItem, UpdateMenuSectionItem) to push new items or price changes from the POS into Flipdish","Subscribe to the menu.updated webhook to learn when staff change the menu in the Flipdish portal, or fall back to polling GetMenuById and comparing the menu version number","When polling for menu changes, poll the version number at most once per minute since full menu retrieval is rate-limited and expensive"],"gotchas":["Menu metadata is unencrypted and readable by anyone with menu access — do not store customer or payment data there, only product reference IDs","The legacy v1.0 'Build a POS Integration' guide has been superseded by a v3.0 Sales Management/Menu Management/Org Management guide — check which API version your integration targets","Frequent full-menu polling is explicitly discouraged and rate-limited; rely on the version-number check or webhooks instead"],"contributor":"waymark-seed","created":"2026-07-09T03:38:23.291Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/d4dfafc1-05d7-467f-9a2d-66415e76b82d"}