15 hours of weekly admin work automated. Pricing errors down 75%.

Global Crafting Supplier manages 3,500 SKUs across B2B and B2C segments. Their pricing structure was genuinely complex. Quantity tiers, customer tags, and material type all feeding into a matrix of rules. The problem wasn't the complexity. It was where the complexity lived.

It lived in spreadsheets. Every week, the operations team spent 15–20 hours manually updating pricing CSVs. When entries were wrong — and they were, roughly 60 times a month — it generated support tickets, eroded trust with wholesale accounts, and burned more ops time to fix. On top of that, a third-party filter app was loading 1.2MB of JavaScript on every collection page, adding 1.5 seconds of latency to the discovery path and driving a 62% bounce rate.

The catalog couldn't scale to 10,000 SKUs under this model. The labor cost would scale with it.

The pricing logic needed to move off spreadsheets and onto the server. I built a Shopify Scripts solution (Ruby) that queries customer tags and line item quantity at checkout initialization and applies the correct pricing rule automatically — zero latency, no manual input, no DOM manipulation on the client side.

The filter app came out next. It was parsing product tags with 1.2MB of injected JavaScript. I replaced it with Shopify OS 2.0 native filtering — Liquid loops querying the Shopify product index directly. No external scripts, instant facet selection, no page reloads.

The page builder dependency came out last. The theme was using a third-party app to manage different layouts for fabric vs. tool product types. I migrated the template architecture to OS 2.0 JSON templates, so layout variants are managed natively in the Shopify Customizer with no app dependency.

Pricing logic in spreadsheets instead of on the server. Once it moved to the server, the labor cost disappeared and the error rate dropped with it. Custom code is an asset. Apps are a liability, and the Global Crafting Supplier engagement made the cost of that liability visible in headcount and tickets.

This engagement also illustrates why the Scripts-to-Functions migration matters now: the pricing automation built here is exactly what Shopify Scripts was designed for, and Scripts stop working in June 2026. If your store has similar logic in Scripts today, the window to migrate is closing.