Switchboard for developers and agencies

Stop rebuilding the sameShopify Functions for every client.

Every store needs its own checkout rules, and every one used to mean the same loop: scope it, build the Function, test it against a live checkout, then maintain it forever. Switchboard is that work, done once, for every Function type, as a product you configure instead of a codebase you own.

The problem

You know the request. "Can we block PO boxes?" "Can we hide COD on big orders?" "Can we stop split shipments?" Each one is a real Shopify Function: a WASM build, an input query, a deploy pipeline, and an API version that will move under you.

So you either eat the hours, quote a number the client won't like, or send them to a pile of single-purpose apps you don't control. None of those feel right, because none of them are.

The toolkit (what you get)

One app covers everyFunction type Shopifyexposes.

Native Shopify Functions running inside checkout, not scripts bolted around it. A Polaris admin your clients can read. Configs in metafields, not code you maintain. When Shopify's API version moves, that's our problem, not yours.

Block orders before they exist. Native Function, every plan.

  • Validation: guard your checkout
  • Discounts: control your pricing
  • Payments: hide, reorder, gate methods
  • Fulfillment: constrain how orders ship
  • Bundles: sell one, ship its components
  • Signed-price cart transforms
  • Delivery: pin and steer pickup
  • Shipping methods: rename, reorder, hide
  • Trust badges at the payment step

The SDK

The part nobodyelse packages.

Most rules are forms. The interesting ones are yours to drive. The storefront SDK lets your code make the call and the checkout obey it:

Signed where it needs to be, capped where it counts. A crafted request can never exceed the limits you set in the admin.

The agency math

The first time a client asks for a checkout rule, it's a project. With Switchboard on the store, every request after that is a config change you can turn around the same day, and bill however you like.

Standardize it across your book: one toolkit on every client store, one place your team already knows, no per-client Function repos to babysit. The Unlimited plan runs as many rules as a complex store needs.

The edges, documented

Straight answers, because you'd find them anyway:

  • Signed-price cart transforms, card hiding (US and Canada), and checkout trust badges require the store to be on Shopify Plus. Shopify's gate, not our pricing.
  • Storefront-driven rules read cart attributes and line properties, so they're built fail-safe: caps clamp values, unknown keys fall back to Shopify's defaults.
  • Functions re-run on cart changes, not on rule saves. The docs cover the test ritual.

Every rule's limits are documented where you configure it. No surprises at checkout.

Pricing snapshot

Free runs one active rule, forever. Paid plans ($10 / $25 / $50) raise how many run at once; Unlimited removes the cap. Every plan can use every capability. 14-day trial on paid plans.

FAQ

Developer objections.

Can I still write custom logic?

Yes. The dev-mode rules exist exactly for that: your code sets the signal, Switchboard's Function enforces it. You get the control without owning the Function.

What happens when Shopify bumps API versions?

We maintain the Functions and the app. Your configs carry forward.

Will it fight the client's other apps?

Our discounts are built to combine rather than block, and one install typically replaces several single-purpose apps that would otherwise collide.

What's actually Plus-gated?

Signed-price cart transforms, card-method hiding in the US and Canada, and trust badges. Everything else runs on every Shopify plan.

Install it on the next client store.The request after that becomes a setting.