E-commerce recipes for AI agents

A single recipe sits on this shelf, and it faces the opposite direction from most of the catalog: capturing what your store sends, not delivering into it. Shopify webhooks aimed at a capture endpoint are stored byte-for-byte, and FlurryPORT never asks for your webhook secret; the signature rides with the capture and only your code verifies it.

Those bytes become test fixtures no hand-written mock can match: a real orders/updated event trailing a cancellation shows up carrying financial_status refunded, a state mock authors rarely model, and a byte-count check against the provider's declared Content-Length turns any quiet reformat into a failing build.

E-commerce is wider than one provider. If your platform posts webhooks, the discipline transfers; the authoring guide at /recipes/authoring is the way onto this shelf.