Traditional ecommerce is built around a short path: browse, cart, checkout. That path is real for many consumer purchases and for some B2B replenishment. It is not how a large share of manufacturer, distributor, and account-based revenue actually moves.
Those transactions run a longer chain: inquiry, configuration, pricing, approval, quote, order, fulfillment, invoice, and exception. A person asks for something that is not a simple add-to-cart. The company has to interpret the request, apply commercial rules, get authority, commit, ship, and bill. Along the way, something will not fit the happy path.
Putting a B2B storefront in front of that chain does not digitize the business if employees still carry the transaction between commerce, CRM, ERP, email, and finance. The site becomes a window. The operating model remains the inbox.
The Storefront Is One Interface, Not the Cycle
B2B commerce is not a consumer storefront with a login. The architectural implication is practical. The digital channel is one way a buyer or a salesperson starts and tracks work. It is not the work.
Inquiry can arrive as an RFQ on the site, an email with a customer part number, a punchout cart, or a call. Configuration may need engineering or a valid option set. Pricing may be contract, not list. Approval may sit with credit, margin, or a plant. The quote, once accepted, has to become an order in the system of record. Fulfillment has to honor what was promised. Finance has to invoice what was shipped, not what someone re-typed.
If any of those steps requires a person to re-enter the same deal, the company has not automated inquiry-to-invoice. It has added a storefront to a relay race.
The goal is not necessarily zero human interaction. Complex B2B still needs people. The goal is that people are not the integration layer. Repeatable work should execute. Commercial rules should hold. Context should survive from the first request to the invoice. Genuine exceptions should arrive to someone with authority, already loaded with the account, the lines, and the reason the process stopped.
What Employees Still Carry
Watch a deal that cannot check out.
The request lands in sales. Someone looks up the account in CRM, the price in ERP, and the stock in a warehouse screen or a 3PL portal. A quote is built in a spreadsheet or a disconnected CPQ. It is emailed. A revision comes back. The approved version is keyed into commerce, or skipped and keyed only into ERP. Fulfillment picks against a different description of the same order. Invoice disputes start because freight, tax, or a substitute never made it into the financial document.
None of that is mysterious. It is the cost of a revenue cycle that was never designed as a single object.
The damage is not only labor. Cycle time stretches while the deal sits between systems. Errors enter at every re-entry. There is no trustworthy view of what is quoted, what is committed, and what is billed. The buyer learns that the website cannot complete the transaction, so the next request never starts there.
Pricing and configuration logic is one critical joint in this chain: the authorized commercial answer. This article is the path that answer must travel afterward, and the path the inquiry must travel before. A perfect price that still has to be re-typed into an order is not an operating model. An elegant portal that still emails finance to invoice is not one either.
Automate the Repeatable Path. Design the Exception.
Most B2B revenue mixes two kinds of work.
One kind should complete without a meeting: a known account, a known SKU or valid configuration, a price already on contract, credit in range, inventory that can be promised. That path should be self-service where the transaction permits it, or at least executable by a salesperson without reconstruction. Inquiry becomes quote becomes order becomes invoice because the systems share the same deal.
The other kind should stop on purpose: a configuration the catalog cannot validate, a discount below the floor, a ship-from that ATP cannot support, a credit hold, a substitution that changes the application. Those stops are not failures. They are the operating model. The failure is when the stop is an inbox with no owner and no context.
The automation gap is the work between systems. Inquiry-to-invoice is that gap stretched across the commercial cycle. Deterministic rules belong on the repeatable path. People belong on the exception, with the record intact.
Do not confuse that design with "making B2B feel like B2C." Convenience helps. Completing the commercial cycle without losing the deal between applications is the requirement.
What Has to Be True at Each Handoff
A useful test is to follow one request and ask, at each handoff, whether the object is still the same deal.
When the inquiry is captured, is it bound to the right account and catalog? When it is priced, is the price the one the order will later honor? When it is approved, is the authority recorded on the same record? When it becomes an order, does anyone type? When it ships, does fulfillment see the quoted configuration? When it is invoiced, does finance start from the order, or from a second reconstruction? When something breaks, does the exception know which quote, which order, and which customer it belongs to?
Connected systems are the backbone that makes those handoffs possible. They are not the cycle. The cycle is the designed sequence of commercial states — requested, quoted, approved, ordered, fulfilled, billed — with an owner for the states that cannot be automatic.
Identity, audit, and write-back are not technical niceties here. If the buyer who requested the quote is not the account that will be billed, the rest of the automation will institutionalize the error.
Build the Cycle, Then Put Surfaces on It
Companies often start with the visible piece: a quote request form, a nicer B2B theme, a portal login. Those surfaces matter only if they sit on a cycle that can finish.
Start instead with the object. Define the deal as it moves from inquiry to invoice. Decide which system owns each state. Connect commerce, CRM, ERP, and fulfillment so the same lines, prices, and quantities persist. Make the repeatable path executable. Give exceptions a route.
Then the storefront, the salesperson's workspace, and even a future buying agent are interfaces into the same operating model. They can start a request, show status, and accept an order without inventing a second version of the truth.
If the new site launched and deals still have to be rebuilt by hand to get paid, the company did not transform B2B commerce. It published a catalog in front of the same relay race.
The leadership question is not whether buyers can browse. It is whether an inquiry can become an invoice without a person carrying the deal between systems that should already share it. If they still have to, the missing work is the cycle — not another theme.