Flagship report

Manufacturer commerce readiness report: the operational truths that decide who launches and who stalls

Manufacturer commerce readiness isn't a platform question. It's an operational question about whether the ERP can answer the questions a commerce site is going to ask it. Across the mid-market manufacturer and distributor engagements Acro Commerce has run, the projects that stall almost always stall in the same places: pricing logic, customer hierarchy, inventory accuracy, and quote workflows. This report sets out what readiness actually looks like and where the breaks happen.

Key takeaway

• Readiness isn't about your platform shortlist, it's about how cleanly your ERP can answer the questions a commerce site is going to ask it.

Executive summary

Mid-market manufacturers tend to start B2B ecommerce projects by shortlisting platforms. Acro Commerce's pattern across discovery engagements is the opposite: the projects that go live on time and stay live are the ones where the ERP-side homework was done first. The platform shortlist is a downstream decision.

This report draws on the readiness patterns we've observed across manufacturer and distributor engagements anchored on systems like Acumatica, as well as engagements with companies running other tier-one and tier-two ERPs. It identifies five readiness dimensions, data, pricing, fulfillment, governance, and people, and explains where most manufacturers are strong, where they break, and what 'ready enough' actually looks like before a build starts.

The headline finding: readiness has very little to do with platform choice and almost everything to do with how cleanly your operational truth is encoded in the systems that already run the business.

Methodology and the basis for these findings

This is not a published external survey. It is a synthesis of the readiness patterns Acro Commerce has observed across the manufacturer and distributor discovery engagements we've run over the last several years, supplemented by the public documentation of ERP and commerce platforms that mid-market manufacturers commonly use, including Acumatica, Shopware, BigCommerce B2B Edition, and Shopify B2B.

The engagements behind this synthesis sit in a recognisable shape: companies with annual revenue between roughly fifteen and three hundred million, complex catalogues (typically 5,000 SKUs and up), customer-specific or contract pricing, dealer or distributor relationships, and quote-heavy buying behaviour. The ERP is almost always already in place; commerce is the new layer being added.

We use the term 'pattern' deliberately. The numbers in this report are observations from engagement work, not survey statistics. Where we cite an external definition or industry concept, available-to-promise (ATP), CPQ, MACH architecture, EDI, we link to a third-party source so the reader can verify the term independently.

The five readiness dimensions: data, pricing, fulfillment, governance, people

Readiness, as we use the term, has five dimensions. The first is data: the cleanliness, completeness, and structural sanity of master data in the ERP. The second is pricing: the company's ability to articulate, not just execute, its pricing logic. The third is fulfillment: whether inventory, availability, and shipping promises can be made truthfully in real time. The fourth is governance: who owns which record, who can change what, and how exceptions are handled. The fifth is people: whether the operations, sales, and IT functions agree on what 'self-service' actually means for their customers.

Of those five, data and pricing are where most manufacturers underestimate the work. Fulfillment is usually a known problem. Governance is often invisible until two teams disagree about who edits a customer record. People, specifically the gap between what sales tells customers and what operations can deliver, is the dimension that most often surfaces late in discovery.

A manufacturer doesn't need to be perfect on all five to launch. They need to be honest about all five before they pick a platform. Across the engagements we've seen, the most common readiness gap is pricing logic that lives in spreadsheets and sales reps' heads rather than in the ERP.

Key observation: where most manufacturers actually break

Across the engagements we've seen, the failure modes are remarkably consistent. The first is item master inconsistency: the same SKU described three ways across ERP, PIM, and the brochure. The second is pricing rules that live outside the ERP, negotiated discounts captured in emails, contract terms held in a sales rep's filing system, volume breaks calculated by hand. The third is inventory that is technically accurate but operationally misleading, because the ERP shows on-hand quantities without netting against committed orders or upcoming production.

The fourth pattern is customer hierarchy. A B2B customer is rarely a single record. It's a parent organization, several billing entities, multiple ship-to locations, and a buying group of named individuals with different permissions. ERPs model this in various ways; commerce platforms rarely model it natively. Bridging that gap is one of the most expensive parts of a B2B ecommerce build, and it's the part most often deferred to 'phase two', a phase that, in our experience, rarely arrives on schedule.

The fifth pattern is the quote-to-order workflow. B2B buying is not catalogue purchase; it is conversation. The companies that launch successfully are the ones that designed their digital quote workflow before they picked a platform, not after. Quote logic is business logic, and business logic belongs in the architecture conversation, not the configuration screen.

Readiness patterns by company size and ERP profile

Readiness varies less by ERP brand than by ERP age and discipline. A ten-year-old Acumatica deployment with clean master data and well-defined pricing dimensions is more ready than a six-month-old deployment of the same product where the implementation cut corners on data governance. The pattern holds across other tier-one and tier-two ERPs. The brand on the badge matters less than whether the implementation respected the company's operational truth.

Company size correlates with readiness, but not in the direction people expect. Smaller manufacturers (under fifty million in revenue) are often more ready than larger ones, because their pricing and customer logic is simpler. The hardest engagements we've seen sit in the hundred-to-three-hundred-million band: complex enough to have meaningful B2B logic, not yet large enough to have a dedicated commerce architecture team.

Industry vertical also matters. Industrial distribution and specialty manufacturing tend to have the most ERP-anchored logic; consumer-adjacent manufacturers (the ones who also sell direct) tend to have lighter ERP dependence but more channel complexity. Both are workable; they require different starting architectures.

The readiness scorecard: what to assess before you shortlist

Readiness is testable. The scorecard we use in discovery covers the five dimensions above as twenty-two questions. Some are technical (can the ERP expose customer-specific price lists via API? does the item master have a single primary identifier per SKU?). Some are operational (when a customer is past due, who decides whether they can still place an order?). Some are organizational (who owns the product catalogue when marketing wants to change a description?).

The scorecard isn't pass/fail. It produces a readiness profile across the five dimensions, plus a short list of 'pre-build' actions, the things that need to be true in the ERP and the operational process before a commerce build starts. Across the manufacturer engagements we've seen, the pre-build action list typically has between four and twelve items. None of them are platform decisions. All of them are decisions a manufacturer can make without an agency in the room.

Acro Commerce's Discovery & Strategy work uses this scorecard as one of several inputs; it's also useful as a self-administered exercise before any agency conversation.

What 'ready enough' looks like in practice

'Ready enough' is not 'perfect.' It is the point at which a manufacturer can write down, in plain language, the answer to seven questions: how is a customer identified, how is a price calculated, how is availability promised, how is a quote turned into an order, who approves what, how does an order get fulfilled and tracked, and what happens when something goes wrong. If those seven answers exist on paper before platform conversations start, the platform conversation gets shorter and the build gets cheaper.

In the engagements where readiness was high, the discovery phase produced a clear architecture brief in four to six weeks and the build phase ran roughly to plan. In the engagements where readiness was low, discovery took longer, the architecture brief kept changing, and the build phase absorbed work that should have happened upstream. The cost difference is large, but the larger cost is timeline: a manufacturer who starts unready typically ships six to twelve months later than a manufacturer who starts ready.

Readiness, in the end, is not an audit. It's a posture. The manufacturers who launch well are the ones who treat their ERP as the operational truth of the business and treat commerce as a new channel through which that truth needs to be expressed. That posture, architecture before app, business logic before platform, is what separates the projects that go live from the projects that get postponed.

Recommendations

First, do the readiness work before the platform work. The platform shortlist will be shorter, the RFP will be sharper, and the implementation partner will be able to give you a more honest estimate. Run the readiness scorecard against your own organization; the questions are answerable without an agency.

Second, name your sources of truth per domain. Pricing, inventory, customer, order, product, each has a system that should own the record. Naming the owner per domain prevents most integration pain. We treat this as a separate discipline in our ERP integration and expansion work.

Third, design the quote-to-order workflow before you design the catalogue. In B2B, the quote is the front door, not the cart. The companies that get this right tend to think of the cart as a quote that has been agreed to, not as a checkout that has been customized.

Fourth, treat 'phase two' with suspicion. Customer hierarchy, approval chains, and contract pricing are not nice-to-haves; deferring them tends to mean rebuilding the data model later at higher cost. If they belong in the operational truth, they belong in phase one.

Fifth, if the readiness picture is mixed, that's normal. Mixed readiness is not a reason to delay; it's a reason to sequence. A good discovery phase converts a mixed readiness profile into a sequenced plan. See Acro Commerce's case studies for examples of how that sequencing plays out across manufacturer engagements.

Frequently Asked Questions

Next step

Get the foundation right before you build.

For readers scoping a platform decision or wanting a full architecture recommendation.