Talk to us

Case study

Peak Distribution: a Shopify B2B integration, live in three weeks.

Patchworks brought Peak Distribution to us in mid-January 2026 with a brief: a Shopify B2B integration on a tight deadline. By early February the contracts were signed; three weeks of build later, the integration went live on 1 March 2026. Three platforms, eight sync flows, a UK to Australia time-zone split. Now running under SLA.

  • Client Peak Distribution
  • Sector B2B distribution, Australia
  • Introduced Mid-January 2026, via Patchworks
  • Contract signed Early February 2026
  • Build window Three weeks from signature to live
  • MVP End of week one
  • Live 1 March 2026
  • Platforms NetSuite · Shopify · SparkLayer B2B
  • Sync flows shipped Eight, end to end
  • Engagement Direct delivery; under SLA from go-live
  • Status Live, under SLA
  • Since launch 3 new D2C brands signed; onboarding via PatchBuddy

The brief

Three weeks. Three platforms. Australia.

The introduction came through Patchworks in mid-January 2026: Peak Distribution needed a Shopify B2B integration on a tight deadline. By early February the contracts were signed and the build window opened. Three weeks. Three platforms (NetSuite, Shopify and SparkLayer B2B). Eight sync flows. B2B-specific behaviours across pricing, credit and invoice settlement. And the team running the project from the Australian side of the planet against our UK delivery.

The time-zone split could have been a delivery risk. Peak turned it into a feature. The team on the Australian side were on-hand for data enrichment, frequent situation-report calls and same-day sign-off on edge cases. Our days ended where theirs began, and vice versa, so the integration advanced overnight in both directions for the full three weeks of build.

The estate

Three platforms, one B2B operating system.

B2B is not D2C with bigger orders. Pricing tiers, credit balances, invoice settlement, purchase-order driven restock visibility, and customer-account hierarchy are all first-class on the Peak Distribution estate. The integration shape reflects that: NetSuite owns the data, Shopify is the customer-facing surface, SparkLayer adds the B2B behaviours on top.

Patchworks Integration platform
  • ERP NetSuite System of record for stock, finance, customers, pricing
  • Storefront Shopify B2B and D2C surface for Peak's trade customers
  • B2B engine SparkLayer B2B Tiered pricing, credit, ordering rules layered onto Shopify

What we shipped

Eight flows, end to end.

Every flow below was scoped, built, tested and live within the three-week build window. No follow-up phases, no “we’ll ship that one later.”

  1. 01

    Sales orders

    Shopify to NetSuite

    B2B and D2C orders captured against the right NetSuite customer record

  2. 02

    Tiered price lists

    NetSuite to SparkLayer

    Customer-group pricing kept in step from the ERP outwards

  3. 03

    Inventory

    NetSuite to Shopify

    Sellable stock published with B2B availability rules in place

  4. 04

    Products

    NetSuite to Shopify

    Item master, attributes, media and channel-readiness

  5. 05

    Customers

    NetSuite to Shopify

    B2B account hierarchy and contact records mirrored to the storefront

  6. 06

    Invoice payments

    NetSuite to Shopify

    B2B invoice settlements visible inside the customer-facing portal

  7. 07

    Credit balances

    NetSuite to Shopify + SparkLayer

    Outstanding credit visible at checkout and in the B2B account view

  8. 08

    Restock dates

    NetSuite PO to Shopify

    Purchase-order-driven restock visibility on out-of-stock SKUs

How a three-week B2B integration actually ships

Pattern depth, not heroics.

Three-week B2B integration delivery isn’t about long hours. It’s about pattern depth and a customer team ready to move at the same pace. The Shopify-to-NetSuite sales-order flow, the NetSuite-to-Shopify inventory and pricing flows, and the B2B credit and invoice surfaces are patterns we have shipped before; they just need to be tuned against this client’s data shape rather than designed from scratch.

What made the deadline real was Peak. Same-hour responses on field-mapping questions. Test data ready before we asked. Decision-makers on the situation-report calls. The engineering side handled the integration; the customer side removed the friction that usually stretches a three-week build into a three-month one.

MVP landed at the end of week one with all eight flows functional against real data. Weeks two and three were UAT, edge-case sign-off and cutover prep, not catch-up. 1 March 2026 was the launch date agreed at signature, and the launch date that actually shipped.

From the platform side

Patchworks called it out on LinkedIn.

“This is not an April Fool, Patchworks can enable Shopify B2B to NetSuite integrations in less than 2 months!

That’s what eCirql by CirqlWorks accomplished for Peak Distribution by taking the Shopify certified, featured in Winter Editions 26 Blueprint and customising it to integrate SparkLayer B2B. Peak Distribution now has automated, secure and scalable integrations for customers, orders, price lists, products and invoices.”
Jim Herbert CEO, Patchworks · LinkedIn

Context The “less than two months” window refers to the full Patchworks deal cycle, from first conversation in mid-January 2026 through to customer go-live. The eCirql build itself was three weeks of that: contracts signed in early February, MVP at the end of week one, UAT and cutover prep through weeks two and three, live on 1 March 2026.

Since launch

Three more brands. Onboarding through PatchBuddy.

Peak has signed three new D2C brands onto the eCirql roster since the March 2026 go-live. All three are onboarding through PatchBuddy, the world’s first AIiPaaS and our own product. Delivery is scheduled by the end of Q2 2026.

The first engagement validated the integration model. The follow-on engagements are validating the delivery model: PatchBuddy absorbing the pattern-heavy build work, our senior team staying on the calls, the architecture and the decisions that actually move a project. Same shape of result, shorter wall-clock time, more capacity for the next client.

Engagement model

Live and under SLA.

Cirql Works delivered the integration directly to Peak Distribution and runs the ongoing support under retainer. Monitoring on every shipped flow, on-call cover, and tiered response SLAs. The engineer who shipped the flow is the engineer answering the support ticket when it matters, time-zone be damned.

Get in touch

Tell us what you’re trying to connect.

And what’s in the way. We will tell you whether we are the right people to do it. Drop us a line below, or open the chat in the corner of the screen.

Direct: contact@ecirql.com