What peak revealed about your integrations
Peak does not break integrations. It removes the slack that was hiding a design fault, and the failure it produces tells you exactly which one.
CATEGORY
Integrations & data posts
Everything we have written on integrations & data — 17 posts, newest first.
17 posts on integrations & data
CategoryIntegrations & data
Freezing your integrations before peak
Freezing your own repository is the easy half. The changes that break peak come from counterparties whose release calendar you have never asked for.
Product feeds for shopping channels
A feed is a view of your product data, not a place to fix it. Most stores need better data in Shopify, not a feed management platform on top of it.
Error budgets for an ecommerce integration
Agree how much failure is acceptable before it happens, measure the business event rather than the HTTP status, and name what changes when the budget is spent.
Marketplace listings and the inventory they will oversell
You cannot make two buyers on two channels take the same unit safely. The design question is not how to prevent oversell — it is how much you will accept, and who pays for it.
ERP-first or Shopify-first: where the catalogue lives
Which system a product is born in decides more about your integration than which connector you buy. Most stores with a real ERP should be ERP-first, and a good number of them should not.
Consent, tracking and a marketing stack that still works
You will measure less than you did, and the honest response is to make the smaller set reliable rather than to buy the precision back. Where the tracking actually breaks is rarely the banner.
The data warehouse question for a mid-market merchant
Most stores asking for a warehouse want four numbers nobody agrees on. A warehouse will not settle the argument — it will just host it at higher cost.
The ecommerce stack diagram every team should have on a wall
One page, eight boxes, and an arrow for every fact that moves. Most integration arguments are really a disagreement about a diagram nobody has drawn.
Product data governance: who is allowed to change what
Nobody owns “products”. Somebody owns price, somebody else owns the SKU, and the argument about who owns the description is the one that breaks your catalogue.
Tax across states, countries and marketplaces
Three different regimes, one order table. The engineering problem is not calculating the tax — it is proving afterwards which registration you collected it under.
Inventory truth: the number three systems disagree about
Shopify, the ERP and the warehouse each show a different figure, and every integration project tries to make them agree. The fix is deciding which one is allowed to be right.
NEXT STEP
Free store audit
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritised list of fixes.