RMG | B2B Ecommerce FAQ

Question 1

What platforms do you build B2B on?

Accepted Answer

Adobe Commerce, BigCommerce B2B, and Shopify Plus B2B, plus headless when catalog scale, pricing complexity, or deep ERP integration justifies it. B2B is one of the few places Adobe Commerce still earns its keep on large catalogs and complex account structures, though Shopify Plus B2B has closed a lot of the gap. We pick based on your catalog, account requirements, and integrations, not on a default. If you’re replatforming, you’ll get an honest recommendation either way.

Question 2

Can you handle customer-specific and contract pricing?

Accepted Answer

Yes. It’s the first thing we scope on a B2B build. Customer-specific price lists, tier and volume breaks, contract and GPO pricing, per-account catalogs, and the quoting flow around them. The hard part isn’t showing a discounted price; it’s keeping thousands of account-specific prices in sync with the ERP in real time and making the right one appear for the right buyer every time.

Question 3

Do you build punchout, EDI, and procurement integrations?

Accepted Answer

Yes. cXML and OCI punchout into Ariba, Coupa, Jaggaer, and SAP, plus EDI for the accounts that still run on it. Punchout is what makes you buyable to enterprise procurement: the session hand-off, the account-specific catalog, and the cart returned to their requisition system all have to work exactly the way their platform expects. We build and test that against the real buyer environment, not a sandbox.

Question 4

Can you integrate with our ERP?

Accepted Answer

Yes, and on a B2B build the ERP integration usually is the project. NetSuite, SAP, Acumatica, Microsoft Dynamics, Infor, and the industry-specific systems. Real-time inventory by warehouse, customer-specific pricing, credit status and holds, order and invoice sync both directions. The edge cases are the work: partial shipments, backorders, freight, credits, and returns. We build middleware and sync logic to handle them rather than hoping a connector covers it.

Question 5

Will our buyers and reps actually use the portal?

Accepted Answer

That’s the metric that decides whether the project worked, so it’s what we design for. Adoption moves on three things: an ordering flow faster than calling a rep, order guides and quick reorder for the SKUs each account buys every week, and rep enablement so your sales team pushes the portal instead of protecting the phone order. Rep-assisted ordering, account dashboards, and commission credit on digital orders are how you get reps on your side rather than working around it.

Question 6

We sell DTC and B2B. Can both run on one platform?

Accepted Answer

Usually, yes, and it’s a common shape. The trap is bolting a wholesale portal onto a DTC storefront and hoping the reps tolerate it. We design both audiences into the same product and pricing architecture, with the catalogs, pricing tiers, checkout, and ordering flows each side actually needs. Where a single platform genuinely can’t serve both, we’ll tell you that in the audit instead of after kickoff.

Question 7

Can you take over a stalled B2B replatform?

Accepted Answer

Yes. Rescue work is one of our engagement models, and stalled B2B builds are the most common version of it. We start with an honest audit of what’s salvageable versus what needs rebuilding, stabilize the critical paths first (ERP sync, pricing, checkout, punchout), then get you back to shipping. No blame, no rip-and-replace by reflex; we keep what works and fix what’s actually blocking launch.

Question 8

How long does a B2B build take?

Accepted Answer

It depends on scope, but you’ll see something real fast: first wins on pricing, catalog, and the ordering flow inside 30 days, with most full B2B builds landing in the 4–8 month range. ERP integration, punchout, and account-hierarchy work add time; a focused portal rebuild on an existing integration moves faster. We scope it precisely in the free site audit before kickoff, so the timeline isn’t a guess.

Comparison criteria	RMG	A DTC agency’s playbook	Your legacy distributor portal
Who is buying	A procurement team with a spec and an approval chain	One shopper, one impulse, one cart	Whoever memorized the part numbers
Pricing	Customer-specific contract pricing, tiers, GPO terms	One price, maybe a discount code	Price files updated by hand, monthly
Catalog	Deep catalogs with real taxonomy, specs, cross-reference	A few hundred clean SKUs	Half a million, none of them searchable
Ordering	Order guides, quick reorder, bulk upload, quoting	Add to cart, check out	Phone, fax, or a PDF order form
Accounts	Hierarchies, roles, budgets, approval workflows	One email, one login	One shared login per company
Checkout	Net terms, POs, punchout (cXML/OCI), credit status	Card only	Call the office to arrange terms
Integrations	NetSuite, SAP, Acumatica, Dynamics: real-time	An app from the marketplace	A nightly CSV, when it runs
What success means	Account adoption, reorder frequency, channel share	Conversion rate	Nobody measures it

Scale the channel.
Arm the sales team.

Every vertical we run B2B in.

Everything the phone order was
covering for, built properly.

Half a million SKUs and a price per account.

The org chart is part of the checkout.

Real-time, or it isn’t integrated.

The portal only wins if the reps want it to.

Nobody loses the account
to the website.

The highest-intent signals you already own.

A call list with the reason attached.

Commission follows the account.

Show you the money.

Here’s what actually changes.

There’s a lot more
to this story.

Get them out
of the way.

Let's audit your storefront.

Scale the channel. Arm the sales team.