BP webhooks can't be filteredThe original push design caused ~7,000 executions a day — everything Brightpearl-side is now pull-based. Never re-subscribe to BP order.*.
Kit-expansion POs fire no webhooksThe personalisation PO is invisible to push integrations, hence the 5-minute settle delay and search pattern in the linking pipeline.
A printed item is a physical "done" signalBrightpearl is always called before printing (both UIs); a BP failure stops the print.
n8n HTTP nodes can't send top-level JSON arraysEvery JSON Patch call to Brightpearl must be a Code node using the httpRequest helper.
The F: drive is the sync mechanismtemplate_configs.json and product_routing.csv are shared files — a nudge or routing edit on one machine is instantly live for all.
