Introduction
Business purchases rarely follow a simple add to cart path. Medusa approval workflows B2B handle the many sign offs those orders require.
Without a structured approval layer, teams rely on emails, spreadsheets, and manual checks, which invites budget leaks and compliance risk.
This platform adds a native approval system on top of its headless B2B starter so that every cart, quote, and order passes through the right approvers before checkout. In this guide you see how those approvals work, how cart locking prevents unauthorized changes, how spend limits shape employee behavior, and how quote workflows connect into the same engine. You also see why an open source stack gives long term control over complex procurement.
Keep reading to see how these pieces fit into a production ready B2B stack.
Key Takeaways
- B2B approval workflows create structured checkpoints for complex purchases. They connect carts and quotes to specific approvers instead of loose email threads. That control reduces unauthorized spend and keeps audits simple for finance teams.
- Cart locking keeps pending baskets frozen while they wait for review. The cart validation workflow hook blocks item edits and checkout attempts until someone decides, so approvers always see the exact basket the buyer submitted.
- Company accounts and roles manage who buys and who approves. Admins define whether orders need review, set personal spend ceilings, and decide who can sign off. That setup works well for distributed teams with many departments and cost centers.
- RFQ workflows, negotiated pricing, and approvals all run inside the same storefront. Buyers move from quote request to fulfilled order without jumping between platforms, which improves conversion. Because the stack is open source, engineering teams can extend these flows instead of waiting for vendor roadmaps.
- Open architecture and a workflow SDK give long term procurement control. Teams can change approval rules, connect ERPs, or add AI features without relying on closed vendor features or pricing tiers.
What are approval workflows and why do B2B teams need them?
Approval workflows in B2B commerce define who must review a purchase before it moves to fulfillment. In a well designed approval system, those reviews become explicit steps inside the platform, not side conversations.
Consumer checkout tends to involve one person, a personal card, and an instant approval from the bank. Business orders often touch department managers, project owners, procurement teams, and finance controllers. Each group has its own budget rules and contracts, so a free for all checkout page cannot meet their needs.
Without automation, those reviews happen in chat threads or shared documents. That feels slow for buyers and makes spend visibility hard for finance, a friction point documented in studies on Authentic Digital Interaction with e-government platforms, which show that fragmented digital touchpoints consistently reduce user trust and transaction completion rates. Research from McKinsey reports that more than 70 percent of B2B decision makers now prefer digital self service, so manual approval chains clash with how people want to buy.
“If approvals live in email, no one can see where a purchase stands,” notes a senior B2B procurement lead. “Putting them inside the commerce system makes spend both faster and easier to control.”
Most standard commerce platforms focus on B2C style flows and provide no approval layer at all or hide it behind costly enterprise contracts and add on tools. Teams then glue together plugins, procurement portals, and custom scripts, which pulls people back into manual coordination. A native approval engine inside the B2B starter avoids that pattern by placing approvals directly in the core checkout and quote flows.
| Platform Type | Impact On B2B Purchasing |
|---|---|
| Native approvals inside commerce platform | One system for buyers, approvers, and finance, with policy enforcement close to the cart |
| No native approvals, or handled in a separate tool | Double data entry, weak visibility, and higher chance of rogue spend or missed approvals |
How the approval module works: Cart locking, dual flows, and spend controls
The approval module in the B2B Starter defines how carts and orders pass through both buyer and seller checks. It introduces company approvals, merchant approvals, and hard cart locking that together enforce purchasing rules without bolted on middleware.
Company approvals apply on the buyer side. An employee shops in the storefront, submits the cart, and then a company admin must review that cart before any order record is created. This matches real world internal flows where budget owners or procurement coordinators sign off on purchases, a pattern supported by research into Investigating Decision-Support Chatbot Acceptance among professionals navigating structured digital decision flows.
Merchant approvals sit on the seller side. They allow the merchant team to inspect incoming orders or quotes before fulfillment, for example to check stock levels, pricing rules, or export restrictions. That second gate is useful for wholesalers, manufacturers, and distributors that run tighter compliance checks.
When a cart enters a pending approval state, the system marks that cart as locked. The cart validation workflow hook intercepts every attempt to add items, change quantities, edit addresses, or start checkout. Only an approval or rejection from the right admin removes the lock, so the version under review always matches what the buyer submitted.
For engineering leaders, this logic lives inside the workflow SDK rather than in hand written patches to checkout code. That keeps custom steps testable and safe when upgrading to new versions of the starter. According to GitHub, the B2B Starter now has hundreds of stars and contributions, which shows active use and maintenance of this approval flow.
At a high level, a typical approval path follows these stages.
- A buyer creates a cart in the storefront and submits it for approval instead of checking out directly. In many B2B flows, that submission is the key signal for the rest of the process. Notifications go to the assigned approver or approver group.
- The approver views the full cart, pricing, promotions, and company metadata in a dedicated screen. They can approve as is, reject, or send feedback to the buyer through comments or internal chat depending on the implementation. Throughout this step, the cart content remains frozen.
- Once approved, the lock is lifted and checkout or order creation runs automatically, often creating a mirrored record in an ERP or accounting system. If rejected, the buyer regains edit rights, adjusts the cart, and can resubmit under the same approval rules. That loop repeats until everyone is satisfied with the order.
Company Level Spend Limits And Role Based Controls
Company level settings decide when approvals trigger and who has the authority to approve. These controls combine company policies, personal spending caps, and role based access in a way that fits real organizations rather than a single template.
- Within the B2B Starter, each company account can toggle whether approval is required on all orders or only above a chosen order total. This gives small teams the option to start with light rules, then raise the bar as purchasing volume grows.
- Company admins also give every employee a personal spending limit. When a cart goes above that limit, the system routes the cart for approval even if the global company setting would not have forced a review. This pattern mirrors how many enterprises manage travel and expense cards.
Only users with an admin role on that company can act on pending approvals. Recent changes to the starter tightened the validation around spending limits and approval state checks, hardening the API so edge cases like split orders or partial approvals do not bypass controls. Procurement studies from PwC show that strong policy enforcement can cut purchasing costs by several percentage points, which explains why these details matter. These approval workflows respect both company wide policy and per user freedom at the same time.
From RFQ to fulfilled order: How quote management connects to approvals
RFQ and quote features plug directly into the same approval engine that guards carts and orders. That link means negotiated deals still follow company rules instead of slipping around them.
In many B2B cases, buyers request custom pricing, volume discounts, or contract terms before they place an order. The storefront lets a buyer start with a quote request, exchange revisions with the merchant, and convert the accepted quote into a cart without retyping lines. The same approval workflows then decide whether that cart can move straight to checkout or must pause for review.
A buyer raises a quote request, often from a saved cart. The merchant estimates pricing, applies the right price list and discounts, and sends back a formal quote. Once the buyer accepts, the platform promotes the quote into a cart that then follows the same approval and checkout steps as any regular cart.
KVY TECH reports that B2B clients who place RFQ, approvals, and payment terms inside one storefront see conversion lift in the range of 38 to 42 percent compared with setups that push buyers into separate procurement portals. That gain happens because buyers never feel they have left the shop to chase approvals.
Case studies on the project site describe how Viessmann turned a rental booking and approval process that once took weeks into a digital flow that completes in minutes. That story highlights what happens when RFQ, approval, and fulfillment all share the same workflow engine.
Why open source architecture gives B2B teams long term procurement control
Medusa’s open source, API first architecture gives B2B teams real control over how approval and procurement rules evolve. Instead of waiting for a closed vendor roadmap, engineering groups can update workflows to match new policies as soon as those policies change.
“Procurement rules change faster than contracts with software vendors,” notes one CTO. “Owning the workflow logic keeps us from being stuck with outdated approval paths.”
The workflow SDK behind these approval workflows lets developers define approval logic as reusable steps. A step might call an ERP such as SAP, write to a CRM like Salesforce, or notify a procurement bot in Slack — an approach aligned with how FDA’s implementation of knowledge-aided assessment frameworks demonstrates that modular, structured decision steps improve auditability and process reliability at scale. Each step runs through clean HTTP endpoints, so the same logic works with web storefronts, mobile apps, or internal portals.
Because the stack is open source under the MIT license, there are no per transaction fees or feature gates blocking advanced approval patterns. The B2B Starter codebase is written almost entirely in TypeScript, with 99.3 percent TypeScript according to GitHub, which keeps compiler checks and editor hints aligned with business rules.
Real deployments underline this architecture. Makro Pro uses this commerce stack to handle wholesale ordering with complex product combinations, while Mitsubishi manages a large catalog of automotive parts on top of the same engine. VeVe, another user of this stack, has processed more than ten thousand requests per second during peak events with no failed transactions, as reported on the project site, showing that the stack holds up under heavy procurement loads.
An implementation partner such as KVY TECH often starts by mapping approval steps with business stakeholders before writing any code. That approach avoids freezing old habits into a new platform and lets the workflow SDK express only the refined process.
Locking in your B2B advantage starts with the right foundation
Securing a B2B edge in procurement means choosing a commerce foundation that respects real approval needs. Native workflows, cart locks, and open architecture together form that foundation.
The first pillar is enforcement through company and merchant approvals plus locked carts. The second pillar is an integrated RFQ to fulfillment flow that avoids separate procurement portals. The third pillar is a workflow engine and open codebase that let teams keep improving approvals over time — a governance model echoed in research on Conformity Assessment of Medical devices, which demonstrates that clear, layered review structures consistently produce more defensible and auditable outcomes.
For teams exploring this stack for complex B2B commerce, working with a senior partner such as KVY TECH shortens the path from idea to live platform. The combination of strong approvals and flexible code turns procurement from a back office chore into a reliable growth channel.
FAQs
Question: Does The Platform Support Multi Level Approval Chains, Or Only Single Admin Authorization?
Yes, Medusa supports single level approvals out of the box, and its workflow SDK lets teams add multi step chains. Developers can define custom workflows where department leads approve first, finance reviews next, and a final approver signs off, all without modifying core files.
Question: Can Approval Workflows In This Stack Integrate With External ERP Or Procurement Systems?
Yes, approval workflows connect to external ERP or procurement tools through the API first design. Approval states, cart locks, and company settings are exposed through HTTP endpoints, so engineers can sync with systems like SAP, Oracle, or Coupa using standard integration patterns.
Question: Is The B2B Starter Production Ready For Enterprise Deployments?
Yes, the B2B Starter is ready for serious production use when implemented correctly. The project ships with integration tests for key company APIs, a mostly TypeScript codebase, regular security updates, and a growing open source community, which together give technology leaders the confidence to run important purchasing flows on it.
Question: What Happens If An Employee’s Cart Is Rejected During The Approval Process?
When an admin rejects a cart, the system removes the lock and returns the cart to an editable state. The employee can change items or quantities, respond to feedback, and resubmit the cart for another approval cycle without losing their previous work or needing a brand new cart.
Question: How Long Does It Typically Take To Implement B2B Approval Workflows On This Stack?
Teams typically implement B2B approval workflows within a few months, depending on complexity. A common pattern is four to six weeks for core setup, six to ten weeks for custom approval, RFQ, and integration work, and additional time for testing, training, and launch activities.
Conclusion
Approval workflows for B2B give teams a practical way to align online checkout with real procurement rules. Company and merchant approvals, spend thresholds, and cart locking handle the governance that spreadsheets and emails used to manage.
Because RFQ flows, quote negotiation, approvals, and checkout all live inside the same B2B starter, buyers stay on one clear path from request to fulfillment. That clarity replaces the common pattern of jumping between catalog, procurement portal, and finance approvals, which wastes time and erodes conversion.
Finally, the workflow SDK and open source architecture keep procurement flexible as policies change or new tools appear. Whether the next step is tying approvals into an ERP, adding AI powered recommendations, or scaling to new markets, a well implemented stack offers room to grow without losing control over how people buy.