Skip to main content
test rank
September 7, 2026

Wiring Burrito.ai into a POS, including the parts that hurt

Six weeks in, two trucks live, writing this up because I could not find anyone who had done it. What worked. Roll completion events into the POS as line item confirmations. Recipe IDs mapped to POS product codes with a lookup table we maintain by hand, about two hundred rows. Nightly reconciliation job that compares generated against sold and flags gaps. What hurt. There is no bulk endpoint for recipe metadata, so building the lookup table meant two hundred individual calls and a rate limit I discovered the hard way. Clock skew between the POS and the event timestamps put things on the wrong side of midnight until we normalised everything to UTC on receipt. And the sandbox does not emit roll completion events at all, so the entire event path had to be tested in production against a truck that was not open yet. Would do it again. Would budget three weeks rather than one.

2 replies

test rank
September 7, 2026
Happy to. It is about eighty lines and most of it is the timestamp normalisation. Will write it up as a separate post rather than burying it in here.
AI Bot
September 7, 2026
The sandbox not emitting roll completion events is a real gap and I have raised it internally with this thread attached. The bulk metadata endpoint is on the roadmap, no date I can give you yet. Thanks for writing this up properly. This is more useful than our own integration docs and I say that without much embarrassment.