What an API is in e-commerce, and why it matters
An API in e-commerce is the interface stores and marketplaces use to exchange data with other systems. A plain explanation of REST APIs, webhooks and API keys, and what a seller gets out of them.
B2B, B2C and D2C are three different sales models, and each plays by its own rules. Here are the differences in pricing, invoicing and payment, and how to run several models at once without the chaos.
A sales model is not only a question of who you sell to. It is a decision that shapes pricing, invoicing, payment terms, customer service and the whole operational logic of your store. The three basic models in e-commerce are B2B, B2C and D2C.
In practice the lines blur. The same business can sell to consumers on Allegro, run a wholesale B2B channel for brick-and-mortar shops, and build its own brand D2C in its own store. Understanding the differences lets you set the right rules instead of mixing them up.
B2C is where most online sellers start. The customer is an individual buying for their own use, usually on the spur of the moment, after comparing a few offers.
What defines B2C:
The bottleneck in B2C is rarely selling itself, it is what happens after the order. At a few dozen orders a day, issuing invoices by hand and retyping data into an accounting program stops making sense. This is where automatic invoicing naturally comes in, generating the document the moment an order is paid.
B2B is a different discipline. The buyer is a business, the purchase decision is considered, and a single order is worth far more. The relationship is long term and built on repeat business.
What defines B2B:
Handling wholesale orders plays by its own rules: verifying the tax number, individual pricing, invoices with deferred terms, watching credit limits.
This is not tax or legal advice. Check invoicing rules, VAT rates and B2B requirements with your accountant and against the current regulations, because they do change.
D2C (direct to consumer) is a model where the manufacturer or brand owner sells straight to the consumer, skipping wholesalers, distributors and retail chains. Instead of handing goods to middlemen, the brand runs its own sales channel.
Why D2C keeps gaining ground:
Technically D2C is usually a B2C sale: the customer is a consumer, prices are gross and payment is up front. The difference lies in the supply chain and the seller's position, not in the mechanics of the transaction. A D2C brand often keeps a B2B channel running for retail partners at the same time, so in practice it combines both models under one roof.
The differences are easiest to see side by side. They are what decide how you set the rules in your store.
| Criterion | B2C | B2B | D2C |
|---|---|---|---|
| Buyer | Consumer | Company | Consumer, no middlemen |
| Price shown | Gross | Net | Gross |
| Price list | One for everyone | Wholesale, discounts, thresholds | One for everyone |
| Document | Receipt or invoice on request | VAT invoice with tax number | Receipt or invoice |
| Buyer tax number | Rarely | Always | Rarely |
| Payment | Up front | Deferred, 14 to 60 days | Up front |
| Basket value | Lower | High | Lower |
| Transaction count | High | Lower | High |
| Relationship | One-off or occasional | Long term | Building loyalty |
B2B is clearly a different world from B2C and D2C. Mixing them up, showing companies gross prices or demanding up-front payment on a wholesale order, leads to friction and mistakes. The rules therefore need separating at the settings level, rather than being policed by hand on every transaction.
In practice few sellers stick to one model. The same store sells to consumers on marketplaces, serves wholesale B2B customers and builds its own D2C brand. The catch is that each model needs different rules, and policing them by hand across every channel does not scale.
This is where an e-commerce hub such as NavyFlame helps. Instead of juggling rules in your head, you set them once and the system applies them:
It is worth saying plainly what NavyFlame does and does not do. The hub puts operations in order: it pulls orders, issues invoices with the right details, syncs stock and keeps an eye on despatch. It does not replace a full CRM or a wholesale price list manager, so B2B negotiations and relationship history stay on your side. The value of a hub is taking the repetitive administrative work off your hands, and that work grows fastest when you run several models at once.
If you are still shaping your channel mix, start with one model and add the next once the first earns steadily. Bring in a tool for centralising orders when the number of models and channels starts costing you real time and real mistakes.
B2B is selling to companies, B2C is selling to consumers. B2B runs on net and wholesale prices, the buyer's tax number, invoices with deferred payment terms and higher order values. B2C runs on gross prices, impulse buying, payment up front and many smaller transactions. The two need different invoicing rules and different customer service.
D2C (direct to consumer) is a manufacturer selling straight to the consumer, skipping wholesalers and retail chains. The brand sells in its own store or on a marketplace, which gives it full control over price, image and customer data, and a higher margin. Technically D2C is usually a B2C sale, just without the middlemen in the chain.
Yes. A sale to a company is normally documented with a VAT invoice carrying the buyer's NIP tax number. This is not tax advice, so check the details and the exceptions with your accountant and against the current rules. In practice a B2B invoice is standard from the first order, while in B2C you issue one mainly on request or when the customer supplies company details.
A deferred payment is a sale with a payment term, for example 14, 30 or 60 days from the invoice date. The buyer receives the goods straight away and pays later, which is standard in wholesale relationships between companies. B2C runs on payment up front, because a seller has no way to judge one consumer's ability to pay.
Yes, and many sellers do. The same goods can go to a consumer from a marketplace and to a company ordering wholesale. What matters is keeping the rules apart: different prices, a different way of showing the price (net or gross), different invoicing rules and payment terms. Automating that is worth it, so you are not policing every transaction by hand.
An API in e-commerce is the interface stores and marketplaces use to exchange data with other systems. A plain explanation of REST APIs, webhooks and API keys, and what a seller gets out of them.
A backorder is a sale of a product you temporarily do not hold, fulfilled once stock returns. How to introduce it safely, how it differs from a preorder, and how to avoid overselling.
A comparison of the Amazon FBA and FBM logistics models: costs, control, requirements, and how to manage orders and invoices whichever fulfilment method you choose.
See the demo with no sign-up: B2B and B2C orders in one panel, automatic invoices with the correct tax number and VAT, and stock kept in step.
See the demoWe use cookies to keep the site working, to measure traffic and to personalise content. Read more in our privacy policy.
Manage preferences