B2B E-commerce Marketplaces: The Selling Side of B2B

B2B e-commerce marketplaces are online platforms where businesses can buy and sell goods and services. They are a valuable resource for businesses of all sizes, as they provide a way to reach a wider audience and to find new suppliers. In this chapter, we will discuss the different types of B2B e-commerce marketplaces and their features.

Learning Objectives

By the end of this chapter, you will be able to:

Classify B2B marketplaces by what businesses buy (direct or indirect goods) and how they buy (spot or long-term contract).
Describe e-distributors, e-procurement networks, exchanges, and industry consortia, with examples.
Explain the benefits and risks of B2B marketplaces for buyers and sellers.
Relate these models to B2B trade in Nepal, including public e-procurement.
Describe the architecture layers of a B2B marketplace and how it integrates with buyers’ and suppliers’ systems through EDI, APIs, punchout catalogues and ERP connections.

Classifying B2B Marketplaces

Two questions sort every net marketplace:

What is bought? Direct goods go into the product itself (steel for a car, flour for noodles). Indirect goods keep the business running but are not part of the product. These are often called MRO goods (maintenance, repair, and operations), such as office supplies, cleaning materials, and spare parts.
How is it bought? Spot purchasing is a one-off purchase at the current market price from whoever offers the best deal. Contract purchasing is a long-term agreement with chosen suppliers at negotiated terms.

	Indirect goods (MRO)	Direct goods
Spot purchasing	E-distributor	Exchange
Contract purchasing	E-procurement network	Industry consortium

1. E-distributors

E-distributors are independently owned intermediaries that offer business buyers a single online catalogue of products from many manufacturers. The e-distributor is the one seller and many businesses buy from it (a one-to-many market). They serve spot purchases of indirect (MRO) goods: a factory that needs a replacement motor or a box of safety gloves today orders from the e-distributor at the listed price. W.W. Grainger is the classic textbook example. Buyers gain one-stop shopping and fast delivery; manufacturers gain access to many small buyers.

2. E-procurement

E-procurement networks are independently owned intermediaries that connect a buying firm with hundreds of approved suppliers for contract purchases of indirect goods. They provide software for the whole purchasing process: catalogues of contracted suppliers, purchase requisitions, approval workflows, purchase orders, and invoice matching. SAP Ariba and Coupa are well-known examples. They help large organizations control spending and enforce negotiated prices.

3. Exchanges

Exchanges are independently owned online marketplaces that connect many suppliers and buyers for spot purchases of direct goods, usually within one industry (a vertical market) such as steel, chemicals, or agricultural commodities. Prices change with supply and demand, sometimes through auctions or bid–ask matching. Exchanges help buyers find the best price, but many early ones failed because established suppliers did not want open price competition.

4. Industry Consortia

An industry consortium marketplace is owned collectively by major players in one sector — for example, several airlines or auto manufacturers funding a shared procurement platform. Members set rules, standards, and sometimes pricing frameworks for their industry. Consortia reduce duplication (one login for many approved suppliers) but can exclude smaller firms that are not members. They differ from public exchanges (open to many buyers and sellers) and from a single company’s private network. Consortia serve contract purchases of direct goods: long-term supply of the inputs that go into members’ products.

flowchart TD
    B2BM[B2B Marketplace Types] --> ED[E-distributor<br/>Indirect goods, spot]
    B2BM --> EP[E-procurement<br/>Indirect goods, contract]
    B2BM --> EX[Exchange<br/>Direct goods, spot]
    B2BM --> IC[Industry Consortium<br/>Direct goods, contract]

Figure 1: Types of B2B E-commerce Marketplaces

flowchart LR
    BUY[Business Buyer] --> PLAT[B2B Marketplace Platform]
    PLAT --> SEL1[Supplier A]
    PLAT --> SEL2[Supplier B]
    PLAT --> SEL3[Supplier C]
    BUY -->|RFQ or Order| PLAT
    PLAT -->|Match and Settle| BUY

Figure 2: Public B2B Marketplace Participants Flow

Comparing the Four Types

Type	Ownership	Goods	Buying style	Main value to buyers
E-distributor	Independent	Indirect (MRO)	Spot	One catalogue, fast delivery
E-procurement	Independent	Indirect (MRO)	Contract	Control of spending and approvals
Exchange	Independent	Direct	Spot	Best market price, many suppliers
Industry consortium	Industry members	Direct	Contract	Stable supply, shared standards

A Worked Example: One Hotel, Three Purchases

A 60-room hotel in Pokhara makes three kinds of purchases:

A broken water pump must be replaced today. The hotel orders from an online supplier of plumbing parts at the listed price. This is a spot purchase of an indirect good, the e-distributor model.
Cleaning supplies and linen are bought every month from three approved suppliers at prices agreed for the year. If the hotel group used purchasing software with approval workflows, this would be the e-procurement model.
Food ingredients go directly into what the hotel sells. If vegetables were bought daily at market prices on an online platform with many farmers and wholesalers, that would resemble an exchange.

Benefits and Risks

For buyers	For sellers
Lower search and transaction costs	Access to more buyers, including in other regions
Price transparency and easier comparison	Lower selling costs than a field sales force
Purchase approvals and records in one system	Faster payment when invoicing is automated
Risk: dependence on platform availability	Risk: price pressure from open comparison
Risk: data shared with the platform owner	Risk: platform fees and commission

B2B E-commerce Marketplaces in Nepal

B2B e-commerce marketplaces are still in their early stages of development in Nepal, but there are a number of platforms that are starting to gain traction.

Some of the most popular B2B e-commerce marketplaces in Nepal include:

Aayo: Aayo is a B2B e-commerce platform that connects manufacturers and wholesalers with retailers. It offers a wide range of products, including food and beverages, office supplies, and industrial equipment.
Nepal Tenders: Nepal Tenders is a portal that provides information about government and private sector tenders in Nepal. It is a valuable resource for businesses that are looking to bid on government contracts.
Foodmandu: In addition to its B2C food delivery service, Foodmandu also offers a B2B service for corporate catering.

These are just a few of the many B2B e-commerce marketplaces that are available in Nepal. As the Internet becomes more widely available in the country, the number and popularity of these marketplaces is likely to grow.

Public e-procurement: Nepal’s largest online B2B buying system is the government’s own. The Public Procurement Monitoring Office (PPMO) runs the electronic Government Procurement (e-GP) system, where public bodies publish tenders and suppliers register and submit bids online. It shows the benefits of e-procurement (transparency, wider competition, records of every bid) and its challenges (supplier training, connectivity, and digital document requirements).

Inside a B2B Marketplace: Architecture and Supply Chain Integration

The four-way classification tells us what kind of marketplace a platform is. This section looks at how it works. A B2B marketplace is more than a B2C shop with bigger orders: buyers expect their own negotiated prices, approval steps before an order goes out, payment on credit, and orders that flow straight into their accounting or ERP system. Each of these needs becomes a layer in the platform’s architecture.

The Layers of a B2B Marketplace

Layer	What it does	Why B2B needs it
Catalogue and product data (PIM)	Stores product names, specifications, units, pack sizes, images and identifiers such as the GTIN	Business buyers compare by specification (cement grade, rod thickness), not by photo
Pricing and contract pricing	Holds list prices, volume tiers and buyer-specific contract prices	Two buyers may see different prices for the same item because of their agreements
RFQ and negotiation	Lets a buyer post a requirement, receive quotes from several sellers and counter-offer	Large or custom orders are rarely bought at a listed price
Order management	Turns an accepted quote or cart into a purchase order; tracks approvals, partial deliveries	B2B orders pass through approvals and often arrive in several shipments
Payments, escrow and credit	Collects payment, holds funds in escrow, or offers credit terms (for example, pay in 30 days)	High-value orders need protection, and many business buyers expect to pay after delivery
Logistics	Quotes freight, books trucks or couriers, shares tracking and proof of delivery	Heavy or bulky goods make delivery cost and timing part of the buying decision
Ratings and trust	Verifies sellers, records ratings and handles disputes	Buyers and sellers often have no previous relationship
Integration	Connects the platform to buyers’ and sellers’ systems through EDI, APIs, punchout and ERP links	Re-typing orders into another system wastes time and causes errors (see the three-way match in 8.2)

Not every marketplace builds every layer. An e-distributor selling stationery needs strong catalogue and order layers but little RFQ; a construction materials exchange needs RFQ, logistics and escrow first.

Architecture at a Glance

The diagram below shows how the layers stack. Buyers and sellers reach the platform through different channels at the top; the bottom layer connects it to the systems each business already uses.

+--------------------------------------------------------------------+
| CHANNELS     Buyer web portal | Mobile app | Punchout session      |
+--------------------------------------------------------------------+
| TRUST        Seller verification | Ratings | Dispute handling      |
| COMMERCE     Catalogue/PIM | Contract pricing | RFQ | Orders       |
| MONEY        Payments | Escrow | Credit terms | Invoices (with VAT)|
| FULFILMENT   Freight quotes | Tracking | Proof of delivery         |
+--------------------------------------------------------------------+
| INTEGRATION  REST APIs | Webhooks | EDI (X12, EDIFACT) | cXML/OCI  |
+--------------------------------------------------------------------+
| BUYER SIDE   ERP or e-procurement system | Accounting software     |
| SELLER SIDE  ERP | Inventory system | Warehouse and delivery tools |
+--------------------------------------------------------------------+

Figure: Layered architecture of a B2B marketplace (simplified)

Integration Methods

Section 3 of the B2B overview (8.1) introduced EDI. In practice a marketplace supports several ways of exchanging data, because its buyers and sellers range from multinationals with ERP systems to shops with a spreadsheet.

Method	How it works	Typical documents	Best suited to
EDI: ANSI X12	Standard message formats maintained by X12; each transaction set has a number	850 PO, 855 PO acknowledgement, 856 ship notice, 810 invoice, 820 payment/remittance	Large trading partners; widely used in North America
EDI: UN/EDIFACT	United Nations rules for EDI, approved and published by UNECE in the UNTDID	ORDERS (purchase order), DESADV (despatch advice), INVOIC (invoice)	International trade between partners in many countries
APIs and webhooks	An API lets one system request or send data on demand; a webhook pushes a message when an event happens	“Order created”, “Order shipped”, stock and price updates	Modern platforms, mobile apps, logistics partners
Punchout (cXML or OCI)	The buyer starts in its own e-procurement system, “punches out” to the supplier’s catalogue, and the cart returns for approval	Punchout request, cart message, then a PO	Companies with procurement systems and approval rules
File upload or portal	Sellers upload price and stock lists as CSV or spreadsheet files; buyers download invoices	Price lists, stock lists, order exports	Small suppliers without ERP systems

EDI standards. X12 describes a supply chain flow in which the buyer sends an 850 Purchase Order, the seller replies with an 855 Purchase Order Acknowledgement, then sends an 856 Ship Notice/Manifest (the advance ship notice, or ASN) and an 810 Invoice, and the buyer pays with an 820 Payment Order/Remittance Advice. UN/EDIFACT covers the same business steps with named messages such as ORDERS, DESADV and INVOIC. Both are mature and reliable but need specialist software and setup for each trading partner.

APIs and webhooks. A REST API lets a distributor’s system ask the marketplace “what new orders do I have?” whenever it wants. A webhook reverses the direction: the marketplace calls the distributor’s system the moment an order is placed. APIs are cheaper to set up than EDI, but each platform defines its own format, so there is less standardisation.

Punchout catalogues. Large buyers want employees to shop from approved suppliers without leaving the company’s purchasing controls. In a punchout, the employee starts in the company’s e-procurement system, opens the supplier’s catalogue, fills a cart, and the cart comes back to the procurement system for approval before a purchase order is sent. Two protocols dominate:

cXML (commerce XML) is a protocol for communication between procurement applications, e-commerce hubs and suppliers. Besides punchout it defines purchase orders, order confirmations, ship notices and invoices.
OCI (Open Catalog Interface) is SAP’s interface for external catalogues. The procurement system sends the catalogue a return address (usually a parameter named HOOK_URL), and the catalogue posts the finished cart back to that address.

ERP Integration

An enterprise resource planning (ERP) system is the business’s main record of products, customers, stock, orders and accounts. The marketplace should not become a second, conflicting record. Good integration decides which system owns each type of data and in which direction it flows.

Data	Usual system of record	Direction	Example trigger
Product master and prices	Seller’s ERP	ERP → marketplace	New price list approved
Stock available	Seller’s ERP or warehouse	ERP → marketplace	Every few minutes or on change
Purchase order	Marketplace (from the buyer)	Marketplace → seller’s ERP	Buyer’s approval completed
Ship notice and tracking	Seller’s ERP or logistics firm	Back to marketplace → buyer	Truck dispatched
Invoice and payment status	Seller’s and buyer’s accounts	Both directions	Goods received; payment made

Three practical rules follow. First, every product, customer and location needs an identifier that both systems recognise. Second, the same order must never be created twice if a message is resent, so each order carries a unique reference that the receiving system checks. Third, failed messages go to an error queue that a person reviews, rather than disappearing silently.

Data Standards: GS1 Identifiers

Integration only works when everyone means the same item. GS1, a global standards body, issues identification keys used in barcodes and electronic messages:

GTIN (Global Trade Item Number) identifies a trade item, which GS1 defines as a product or service that is priced, ordered or invoiced at any point in the supply chain. GTINs come in four lengths: GTIN-8, GTIN-12 (the UPC-A barcode), GTIN-13 (the EAN-13 barcode) and GTIN-14, which identifies groupings such as a carton or case and is not scanned at the till.
GLN (Global Location Number) identifies parties and locations, such as a warehouse or delivery point.
SSCC (Serial Shipping Container Code) identifies a logistic unit, such as a pallet, so that it can be tracked from the ship notice to the receiving dock.

GS1 recommends that systems store every GTIN in 14-digit form (padding shorter ones with leading zeros), so a marketplace, a distributor’s ERP and a retailer’s point-of-sale system all match the same number. A company obtains its GS1 Company Prefix, from which it creates GTINs, through a GS1 Member Organisation; GS1’s “Get a barcode” page lists Nepal among the locations from which a business can find the official route. GS1 also publishes GTIN guidance for construction products, which matters for building-materials marketplaces.

Three Real Marketplaces, Layer by Layer

These examples are described only from the companies’ own published pages; no performance figures are claimed here.

Alibaba.com (global, cross-border). Its Request for Quotation market lets a buyer post a sourcing request to the platform rather than to one seller, and sellers respond with quotes. Trade Assurance is Alibaba.com’s order protection: the buyer pays through Alibaba.com, the payment is held in escrow and released to the supplier after the product is received and confirmed, and Alibaba.com mediates if order terms are not met. Protection applies only to orders paid through the platform. Layers shown: RFQ, escrow, trust and disputes.
Amazon Business (procurement integration). Amazon Business supports punchout: buyers start in their e-procurement system, punch out to Amazon Business and route the cart back for approval. Amazon Business states that more than 200 e-procurement systems integrate with it, and it also offers punch-in, integrated search and hosted catalogue options; its technical guides use cXML and OCI. Layers shown: integration, order management, approvals.
Udaan (India, wholesale to small retailers). Founded in 2016 and based in Bengaluru, Udaan describes itself as an eB2B platform serving retailers in categories including FMCG, staples, fruits and vegetables, and pharma. It offers a trade credit (deferred payment) facility to eligible business buyers at its discretion, and udaanCapital provides working-capital finance. Layers shown: catalogue for small shops, credit terms, logistics.

Nepal Context: Applying the Layers

The two Unit 8 teaching cases are composites, but they map neatly onto this architecture.

In the construction materials marketplace case, the platform built the RFQ and negotiation layer (counter-offer chat), the logistics layer (truck capacity, lead times, route pricing) and a trust layer (verified stock locations and escrow for orders above Rs. 2,00,000). Its next integration step would be daily price and stock feeds from suppliers, by API for larger dealers and by spreadsheet upload for small ones, plus VAT invoices that contractors can import into their accounting software.
In the FMCG private industrial network case, the company used standard product IDs and EDI or APIs for orders, ship notices and invoices. GTINs on consumer packs and GTIN-14s on cartons let head office, distributors and the retailer app count the same item. The case is a private network, not an open marketplace, but the integration layer is the same.

Many Nepali SMEs keep accounts in local accounting software or spreadsheets rather than a full ERP, and credit is still often recorded in paper ledgers (see 8.1). A marketplace serving them should therefore start with simple file uploads, clear digital invoices and a credit-terms module, and add APIs and EDI as larger partners join.

Summary

B2B net marketplaces are classified by what is bought (direct or indirect goods) and how (spot or contract). E-distributors sell indirect goods on the spot from many manufacturers’ catalogues; e-procurement networks manage contracted purchases of indirect goods; exchanges match many buyers and sellers of direct goods at market prices; industry consortia give members long-term, standardised supply of direct goods. Marketplaces lower search and transaction costs, but they bring price pressure, fees, and dependence on the platform.

Inside, a B2B marketplace is built in layers: catalogue and product data, contract pricing, RFQ, order management, payments with escrow and credit, logistics, ratings, and an integration layer. Integration uses EDI (X12 or UN/EDIFACT), APIs and webhooks, punchout through cXML or OCI, and simple file uploads, all tied to each firm’s ERP or accounting system. Shared identifiers such as GS1 GTINs make sure every system means the same item.

Key Takeaways

Direct goods go into the product; indirect (MRO) goods keep the business running.
Spot buying is one-off at market price; contract buying is long-term at agreed terms.
E-distributor = indirect + spot; e-procurement = indirect + contract; exchange = direct + spot; consortium = direct + contract.
Buyers gain price transparency and control; sellers gain reach but face price pressure.
Nepal’s e-GP system is a large, real example of public e-procurement.
B2B marketplaces add layers B2C shops rarely need: contract prices, RFQ, approvals, escrow and credit terms.
EDI, APIs, punchout and file uploads all move the same documents (PO, acknowledgement, ship notice, invoice); the right choice depends on the partner.
The ERP stays the system of record; the marketplace must not become a second, conflicting copy.
GTINs (and GLNs and SSCCs) give products, places and pallets one shared number across the chain.

Discussion Questions

Why did many independent exchanges fail while industry consortia survived?
Which marketplace type fits a pharmacy chain buying medicines every month from fixed distributors?
What changes for small suppliers when a government moves tendering online?
A Nepali construction marketplace can afford to build only two more layers this year. Which two would you choose, and why?

Exam-Style Questions

Short answer

Differentiate between direct goods and indirect goods.
What is the difference between spot purchasing and contract purchasing?
What is an e-distributor? Give an example.
What is a punchout catalogue? Name the two common punchout protocols.
What is a GTIN, and why should a marketplace store it for every product?

Long answer

Explain the four types of B2B net marketplaces using the direct/indirect and spot/contract classification.
Discuss the benefits and risks of B2B marketplaces for buyers and sellers, with reference to Nepal.
Describe the main architecture layers of a B2B marketplace. Using the construction materials case, explain which layers that platform built and why.
Compare EDI (X12 or UN/EDIFACT), APIs with webhooks, and punchout as ways to integrate a marketplace with buyers’ and sellers’ systems. Which would you recommend for (a) a multinational FMCG distributor and (b) a small hardware shop in Pokhara? Justify your answer.

Unit 8.4: B2B E-commerce Marketplaces: The Selling Side of B2B