B2BIntegrationsMiddleware

One seamless B2B flow from two disconnected systems

A premium wholesale-only B2B storefront needed rich product customisation and full B2B cart/checkout simultaneously — two specialist systems that don't natively share data. We built the bridge, wired in SparkLayer's native Sales Agent ordering for reps, and added the access layer.

StickerCactus Client
B2B / Custom Stickers Industry
3 integrations Scope
Unified B2B stack Outcome
StickerCactus B2B stack — Teeinblue, SparkLayer, and Locksmith unified
About the client

StickerCactus — premium B2B custom sticker operation

StickerCactus is a premium, wholesale-only B2B storefront specialising in custom stickers. Their buyers need rich product customisation — upload artwork, choose finishes, specify quantities — and a full B2B cart and checkout experience.

The challenge was that product customisation (Teeinblue) and B2B commerce (SparkLayer) each owned part of the flow but weren't built to share data. Customisation details had to bridge into the B2B cart structure, sales reps needed to place orders on behalf of wholesale accounts, and access control needed to be granular per B2B customer.

Project at a glance
Client StickerCactus
URL stickercactus.com
Platform Shopify
Scope 3 integrations
Outcome Unified B2B stack
The challenge

Two specialist apps, zero native integration

Product customisation and B2B commerce are both complex individually. StickerCactus needed both simultaneously — and the two systems weren't built to work together.

01

Customisation data not reaching the B2B cart

Teeinblue captured customisation details — artwork, specs, finishes — but SparkLayer's B2B cart had no way to receive or display that data, creating a gap at the most critical step.

02

Rep ordering not connected to customisation

SparkLayer's Sales Agent ordering let reps place orders for wholesale accounts, but it wasn't connected to the Teeinblue customisation flow — so rep-assisted orders couldn't carry the custom product details cleanly.

03

Access control needed per B2B customer

Different wholesale accounts needed to see different product lines — but access control was all-or-nothing with no way to gate at the account level.

04

Two-system maintenance overhead

Without a bridge layer, any change to product customisation or B2B pricing required manual reconciliation between both systems — an ongoing drain on operations.

Teeinblue to SparkLayer integration architecture — the data gap
The constraint

Teeinblue and SparkLayer don't share data natively

Teeinblue (product customisation) and SparkLayer (B2B commerce) each own part of the flow but aren't built to share data, so customisation details and the B2B cart structure had to be bridged with custom logic.

  • Teeinblue's customisation output format doesn't map to SparkLayer's cart line-item structure.
  • SparkLayer's native Sales Agent ordering handles rep-assisted orders, but it wasn't connected to Teeinblue's customisation output.
  • Locksmith's product visibility rules needed to work at the B2B account level, not just site-wide.

The approach: build a custom bridge layer between the two apps, connect SparkLayer's native Sales Agent ordering to the customisation flow, and use the Locksmith API to enable granular account-level access control.

Our solution

Bridge, rep ordering, and access control as one system

UpSolite configured and optimised Teeinblue for premium customisation, built custom logic to bridge Teeinblue's customisation data into SparkLayer's B2B cart, integrated SparkLayer's native Sales Agent ordering so reps could place complete orders on behalf of wholesale accounts, and implemented Locksmith API logic to manage B2B menu access and product restrictions.

  • Custom middleware bridges Teeinblue customisation data into SparkLayer's B2B cart — no manual reconciliation.
  • SparkLayer's native Sales Agent ordering, connected to the customisation flow, lets reps place complete orders on behalf of any wholesale account with full cart and pricing visibility.
  • Locksmith API controls product and page visibility per B2B customer — granular, per-account access rules.
  • End-to-end: customisation, B2B checkout, rep ordering, and access control working as one system.
SparkLayer Sales Agent ordering connected to Teeinblue customisation flow
What we delivered

Three integrations, one unified B2B operation

01
Teeinblue + SparkLayer integration bridgeMiddleware

Custom middleware syncing customisation data, pricing tiers, and product configuration between Teeinblue and SparkLayer — ensuring consistent data across both systems with no manual reconciliation.

Custom middlewareTeeinblue APISparkLayer APIData sync
02
SparkLayer Sales Agent integrationRep ordering

Connected SparkLayer's native Sales Agent ordering to the customisation flow, so reps can log in as a wholesale customer and place complete custom orders on their behalf — with full cart and pricing visibility.

SparkLayer Sales AgentRep orderingCustomisation flowWholesale
03
Locksmith API access controlAccess control

Leveraged the Locksmith API to implement granular product and page access rules based on customer tags — giving precise control over which wholesale accounts see which product lines.

Locksmith APICustomer tagsPer-account rulesProduct gating
Results

Customisation and B2B checkout working as one

Primary outcomeZeroManual sync required between Teeinblue and SparkLayerCustom bridge handles data flow automatically across both systems
Seamless Customisation flows directly into B2B checkout
Reps Can place complete orders for any wholesale account
Per-account Product access controlled at the customer level
Zero Manual reconciliation between the two systems
Before
Customisation to cart Manual gap between systems
Rep-assisted orders Custom orders done manually
Product access control All-or-nothing
System reconciliation Manual, ongoing
After
Customisation to cart Automatic via bridge
Rep-assisted orders Integrated via SparkLayer Sales Agent
Product access control Per B2B account
System reconciliation Automated bridge
The work

Screenshots from the delivered integration

Teeinblue product customisation interface
Customisation flowArtwork, finish, spec — captured at source
SparkLayer B2B cart with custom data synced
B2B cart — data bridgedCustom specs visible inline in cart
SparkLayer Sales Agent rep ordering
Sales Agent orderingReps place orders for any wholesale account
Locksmith per-account access control
Per-account accessProduct visibility gated by B2B account
Full B2B stack — three systems unified
Unified B2B stackThree integrations, zero manual sync
Our tech stack

Three specialist tools, one custom bridge layer

Teeinblue and SparkLayer each do their job well — the integration bridge and Locksmith API layer are what tie them into a single, coherent B2B operation.

Teeinblue
SparkLayer
Locksmith API
Custom Integration Logic
Shopify Admin API
Shopify Liquid
Customer Tags
Approach & timeline

Integration-led, configure then bridge

Integration-led build: configured each system independently to its optimal state, then engineered the bridge and access layer between them — ensuring each component was solid before connecting them.

Common questions

What a B2B integration build actually involves

Questions we often hear before a complex app integration or B2B tooling build.

Where apps have APIs or webhook outputs, yes — we build the middleware that translates between their data formats. The complexity depends on how different the data models are.
Using SparkLayer's native Sales Agent ordering — now connected to the customisation flow — reps can log in as any wholesale customer, see their exact pricing, and place complete custom orders on their behalf.
When used via the API with native Liquid logic, visibility rules are evaluated server-side during Liquid rendering — no client-side overhead on page load.
We build the bridge with version-aware API calls and document the integration. If an app updates its API, the bridge needs an update — we scope this as part of ongoing support.
Complex integrations, made to work

Running apps that aren't talking to each other?

Whether it's bridging two systems, connecting wholesale rep ordering, or implementing access control — let's make your B2B stack work as one.

See how we approach B2B commerce →