Buying from another business is nothing like buying from a shop. There are contracted prices instead of list prices, several people on one account instead of one shopper, an approval chain instead of a checkout button, and credit terms instead of instant payment. A B2B procurement platform is the software built for that reality. This guide explains what such a platform does, how marketplaces differ from private platforms, and gives you a supplier onboarding template, a punchout checklist and two worked examples.
Key takeaways
- B2B buying runs on contracted pricing, approvals, credit terms and multi-buyer accounts, none of which consumer carts handle.
- Marketplaces win on discovery and long-tail spend; private platforms win on control, contracts and audit.
- Punchout catalogues give buyers the supplier full range while keeping your approval rules intact.
- The platform is the front end of buying; the ERP stays the financial system of record, joined by integration.
What a B2B procurement platform actually is
A B2B procurement platform is the software an organisation uses to buy goods and services from its suppliers under agreed commercial terms. It is the place where a need becomes a requisition, a requisition becomes an approved purchase order, an order becomes a delivery, and a delivery becomes an invoice that can be paid with confidence. Everything in that chain is recorded, linked and searchable, which is what separates a platform from a shared inbox and a spreadsheet.
The term overlaps heavily with e-procurement, and in practice the two are used interchangeably. The useful distinction is emphasis. E-procurement describes the digitisation of the buying process in general; a B2B procurement platform describes the specific system that connects a buying organisation to its trading partners. If you want the wider process view first, our e-procurement platform guide covers the full lifecycle, and this article focuses on the business-to-business mechanics that sit on top of it.
Most platforms today are delivered as software as a service, which matters more than it sounds. Because suppliers, buyers, approvers and finance all need access, and because they rarely sit on the same network, a browser-based service with role-based permissions is the only practical shape. Suppliers log in to the same system their customers use, which removes the file exchanges and email chains that cause most procurement disputes.
How B2B buying differs from consumer buying
Every difference below explains a feature you will find in a serious procurement platform and will not find in a retail cart. When you evaluate software, these are the mechanics to test rather than the interface polish.
- Contracted pricing. The price a buyer sees is the one negotiated in their contract, not a public list price. The same product may carry three different prices for three different customers, and prices step down at volume breaks.
- Approval chains. The person who needs the item is rarely the person allowed to commit the money. Value thresholds, cost centres and category rules decide who signs, and the platform has to route accordingly.
- Credit terms. Payment happens on terms, typically thirty to sixty days after invoice, not at the moment of order. That makes the invoice, not the payment, the event the system revolves around.
- Punchout catalogues. Buyers need the supplier live range with current stock, but the buying organisation needs the controls. Punchout satisfies both by sending the shopper out and bringing the basket back.
- Multi-buyer accounts. One customer account carries dozens of users across sites and departments, each with their own permissions, budgets, delivery addresses and default cost codes.
- Three-way matching. An invoice is only paid when it agrees with the purchase order and the goods receipt. Consumer commerce has no equivalent because nothing is received on credit.
Marketplace versus private platform
The two dominant models answer different questions. A marketplace answers "where can I buy this?" and a private platform answers "how do we buy this properly?". Both are legitimate, and the mistake is choosing on brand rather than on the shape of your spend.
| Dimension | B2B marketplace | Private procurement platform |
|---|---|---|
| Supplier base | Open, thousands of sellers you have not vetted | Closed, only suppliers you have onboarded |
| Pricing | Mostly listed, some negotiated tiers | Contracted rates per supplier and per volume break |
| Approvals | Basic spend limits per user | Full rules by value, category, cost centre and site |
| Best for | Long-tail, low-value, urgent or one-off buying | Repeatable, contracted, budgeted and audited spend |
| Data ownership | Shared with the marketplace operator | Yours, held in your instance |
| Audit trail | Order history only | Request, approval, order, receipt, invoice, payment |
| Typical cost model | Commission on transaction value | Subscription by user or module |
In practice most organisations run both. The private platform is the system of record and holds the contracted spend that makes up the bulk of the value, while a marketplace or two is connected for the unpredictable tail. The important rule is that even marketplace orders should be raised through the platform so that commitment, receipt and invoice still land in one place. A shortlist of tools that handle this well is in our roundup of the best e-procurement software.
A supplier onboarding template
Onboarding is where most B2B platforms succeed or quietly fail. If suppliers are added carelessly, every downstream control is built on sand. The template below describes the four blocks of information to collect before a supplier can receive a single order, and it works as well on a form as it does in a workflow.
Block one: identity
Legal entity name, trading name, registered address, company registration number, tax or VAT number, and the primary trading contact. This block proves the supplier exists and is who they claim to be.
Block two: financial
Bank account details with independent verification, remittance email, currency, payment terms and any early settlement discount. Verify bank changes by callback, never by email alone.
Block three: compliance
Insurance certificates with expiry dates, relevant accreditations, sanctions and beneficial ownership screening, and signed acceptance of your standard terms and code of conduct.
Block four: commercial
Contract reference and end date, agreed price list or rate card, lead times, minimum order values, delivery locations served, and the catalogue method: hosted, punchout or free text.
Two rules make the template work. First, every field has an owner, so identity and compliance belong to procurement while financial details belong to finance, and no single person can create a supplier and pay it. Second, dated fields expire. Insurance certificates and price lists carry review dates that trigger a task, which is how a supplier record stays trustworthy in year three rather than only on day one.
Punchout and catalogue checklist
Catalogues are the difference between a platform people use and one they avoid. Work through this checklist for each supplier before you switch their catalogue on.
Decide the catalogue type per supplier, not per platform. Hosted catalogues suit stable, small ranges where prices change a few times a year. Punchout suits large or fast-moving ranges where the supplier site is the only reliable source of stock and configuration. Free text suits genuine one-offs. Forcing all three suppliers into one model is the most common cause of stale prices and rogue buying.
The checks that matter: confirm the punchout connection returns the contracted price rather than the public one, and test it with a real buyer login; check that the returned basket carries part numbers, units of measure and tax codes your system understands; map every returned line to a category code so reporting stays clean; agree who updates a hosted price file and how often; test what happens when an item is discontinued mid-basket; set a maximum basket value that triggers a different approval route; and confirm that the supplier order acknowledgement flows back so buyers can see confirmed delivery dates without ringing anyone.
Example one: a distributor catalogue buy
A facilities team buys consumables from an industrial distributor with a forty thousand line range and a negotiated discount off list. Hosting that catalogue would be unworkable, so the supplier is connected by punchout. A site supervisor raises a requisition, punches out, fills a basket with filters and fixings at contracted prices, and returns. The basket becomes a requisition worth 640, which sits below the site threshold of 1,000 and is auto-approved against the maintenance budget.
What is worth annotating here is what the platform did quietly. It stamped the cost centre from the supervisor profile, so nobody had to remember a code. It checked the budget before releasing the order rather than after the invoice arrived. It sent the order electronically, so the distributor keyed nothing and mis-keyed nothing. When the goods arrived, the supervisor receipted on a phone, and the invoice matched to order and receipt automatically. The whole cycle consumed about four minutes of human attention and produced a complete audit trail. That combination is the return on a B2B platform in ordinary, high-frequency spend.
Example two: a services buy
Now a marketing manager needs a research agency for a 45,000 project. There is no catalogue, no part number and no delivery note, which is exactly where weak platforms fall over. The requisition is raised as a free-text services request with a scope document attached. Because the value crosses two thresholds, the approval routes to the department head and then to finance, and because the category is professional services it also picks up a legal review step for the contract.
The order is raised against a rate card rather than a unit price, and receipting works by milestone. When the agency completes phase one, the manager receipts 15,000 of the order value, which releases the first invoice for matching. The remaining commitment stays visible in budget reporting, which is the part spreadsheets never manage. Services spend is usually the largest and least controlled slice of procurement, so a platform that handles milestones, rate cards and partial receipting is worth more here than anywhere else.
Integrating with your ERP
A procurement platform is not a replacement for your finance system, and any vendor who suggests otherwise should be treated carefully. The platform owns the buying process; the ERP owns the ledgers. Four integration points do almost all the work. Supplier master data flows from the ERP so the platform never invents a supplier. Budgets and cost centre structures flow the same way so approvals check against real numbers. Approved purchase orders flow out from the platform as commitments. Matched invoices flow out ready for payment, with the match result attached.
Get the direction of travel clear before build. Decide which system is master for each data object, agree how failures are surfaced and retried, and insist on a reconciliation report that shows any record stuck between the two. Most integration pain comes not from the technology but from an unresolved argument about who owns the supplier record. Our platform guide sets out the same decisions in the context of a wider suite rollout.
A rollout checklist that works
Rollouts fail on adoption, not on software. The sequence below has a good track record because it puts early value where the volume is and leaves the hard categories until the team is confident.
Start by ranking spend and picking the top three suppliers by transaction count, not by value, because frequency drives habit. Onboard those suppliers fully using the template above. Configure approvals to match how decisions are genuinely made today, then simplify later; encoding an aspirational process on day one guarantees workarounds. Connect the ERP for suppliers and budgets before go-live, and leave invoice flow until orders are stable. Train by role rather than by module, so a requester learns requesting and an approver learns approving. Run a four-week pilot in one department with a named sponsor. Measure three things only: percentage of spend raised through the platform, average approval time, and first-time match rate. Then add suppliers in waves, and review catalogue accuracy each quarter for as long as the platform lives.
Done in that order, a B2B procurement platform stops being an IT project and becomes the default way people buy, which is the only definition of success that matters. If you would like to see how ProcureWave handles punchout, multi-buyer accounts and ERP integration for your own categories, take a look at what our solution covers and get in touch whenever you are ready for a walkthrough.
Frequently asked questions
What is a B2B procurement platform?
A B2B procurement platform is software that lets one business buy from another under agreed commercial terms. It holds the supplier list, the contracted prices, the approval rules and the order and invoice records, so that a purchase follows a controlled path from request to payment rather than an ad hoc email or card payment.
How is B2B buying different from consumer buying?
Consumer buying is one person paying a list price immediately. B2B buying involves negotiated pricing, multiple people on one account, an approval chain, credit terms rather than instant payment, and an invoice that has to be matched to an order and a receipt before it is paid.
Should we use a marketplace or a private procurement platform?
Marketplaces suit long-tail, low-value buying where discovery matters more than control. A private platform suits contracted, repeatable spend where you need your own prices, your own approval rules and your own supplier records. Most organisations end up running both, with the private platform as the system of record. Our procurement platform guide compares the models in more depth.
What is a punchout catalogue?
Punchout lets a buyer leave the procurement platform, shop inside the supplier own website at contracted prices, and return with a filled basket that becomes a requisition. The buyer gets the supplier full, current range; the buying organisation keeps the approval and budget controls.
Does a B2B procurement platform replace our ERP?
No. The platform handles the front end of buying, which is requesting, approving, ordering and receipting. The ERP remains the financial system of record for ledgers, payments and reporting. The two are joined by integrations that sync suppliers, budgets, orders and invoices.
Want to see this in your own numbers?
Book a tailored demo and we will show ProcureWave running on scenarios that match your business.
Get in touch
