FAB Commerce · Commerce

E-Commerce & Marketplace

Unify store and marketplaces around one stock and order truth.

Infrastructure that runs your own store and marketplace channels from one stock record, using sellable-stock logic to prevent overselling.

  • One stock, many channels
  • Lower overselling risk
  • Orders in a single pool
FAB Commerce channel stock and order pool screen
Product tour

FAB Commerce, screen by screen.

FAB Commerce · Channels & orders

One stock, many channels.

Available stock is published per channel share; every channel’s orders in one pool.

  • Sellable stockReserved, in-transit and blocked stock deducted before publishing to channels.
  • Multi-channel syncPer-channel stock allocation, latency tolerance and update ordering.
  • Order poolOrders from all channels in one screen with the channel label preserved.
  • Channel pricingPricing rules that account for commission and shipping per channel.
  • Returns and cancellationsChannel return flows, restocking and accounting entries.
FAB Commerce channel stock and order pool screen
How it works

From channel to shipment, and back as a return.

CH

Channel order

Arrives from store and marketplaces with its channel tag.

POOL

Order pool

All channels on one screen.

STK

Stock reservation

Reserved, in-transit and blocked stock deducted; overselling risk drops.

SYN

Channel sync

Channel share, latency tolerance and update order.

SHP

Shipping & e-document

Cargo and e-documents together with ERP.

RET

Return

Channel return flow, back to stock and accounting entry.

Who uses it?

Every role sees its own screen.

  • E-commerce operations

    Order pool and channel status.

    Order pool
  • Channel manager

    Channel pricing and stock share.

    Pricing
  • Warehouse

    Shipping and returns.

    Returns
  • Finance

    Channel cost incl. commission and cargo.

    Channel cost
Integration surface

The product is not an isolated island.

Data ownership, error handling, security and audit trails are designed as part of the implementation.

  • E-commerce and marketplaces
  • ERP and accounting
  • Banking and payment services
  • Cargo and logistics
  • e-Document services
  • REST API · Webhook

What is e-commerce and marketplace management?

For businesses selling through several channels the real problem is not the storefront but stock consistency. When the same item is listed on your own site and several marketplaces, the delay between stock updates turns directly into overselling.

Which problem does it solve?

  • Overselling. Late channel stock updates sell items you do not have, hurting cancellation rates and channel performance scores.
  • Orders scatter across channels. Each channel has its own panel and there is no combined view.
  • Channel profitability is unknown. Without deducting commission, shipping and return costs, you cannot see which channel earns money.

How it works

What is published to channels is sellable stock, not raw stock: reserved, in-transit and blocked quantities are deducted. A per-channel safety margin can also be defined; on fast-moving items that margin prevents overselling.

Stock updates are queued, with a separate latency tolerance per channel. If one channel's API stops responding, updates to the others continue; failed updates are retried and the number of attempts is recorded.

Orders land in a single pool while keeping their channel label, because return conditions, shipping agreements and commissions differ by channel.

Modules

  • Products and variants: per-channel titles, images and category mapping.
  • Stock: sellable stock calculation, safety margin, channel allocation.
  • Orders: pool, status tracking, partial shipment, shipping labels.
  • Pricing: rules that include channel cost, campaigns, competitive tracking.
  • Returns: reason codes, restocking decisions, accounting entries.
  • Reporting: revenue per channel, cancellation and return rates, net channel profitability.

Integrations

Marketplace channels, shipping carriers, payment providers and virtual POS (fintech infrastructure), e-invoicing and e-archive, ERP for items, stock, orders and accounts, retail POS for store stock, and bank integration for collection reconciliation.

Architecture notes

  • Channel connections are monitored individually and raise alerts when one stops.
  • Stock updates are idempotent: sending the same update twice changes nothing.
  • Order retrieval is deduplicated so the same order is never imported twice.
  • Channel category and attribute mappings are held as data, not hard-coded.

Usage scenarios

  • Manufacturer to consumer: own store and marketplaces together.
  • Retail chains: publishing store stock to the online channel.
  • Wholesale plus retail: dual channels over the same stock with the dealer portal.
  • Export: multi-currency with per-country pricing and shipping rules.

Roll-out

  1. Product data: category mapping, image and title standards.
  2. Stock policy: sellable stock definition, safety margin, channel allocation.
  3. Order flow: pool, fulfilment, shipping and invoicing.
  4. Measurement: channel profitability, cancellation and return rates.

Frequently asked questions

Should we publish store stock online?

You can, provided store count accuracy is reliable. Publishing store stock without it is the most common cause of overselling.

How many channels can be managed at once?

The limit is operational rather than technical: each channel has its own return conditions, shipping agreement and content rules. As channel count grows, managing those rules becomes the real cost.

Why this instead of a packaged e-commerce platform?

For a standard storefront, a packaged platform is usually the better choice. The difference appears when you need one stock record shared with the ERP, industry-specific variant structures (colour/size matrices, multiple units) or marketplace-specific rules.

See the product with your process

Let’s plan a demo around your workflow—not a generic presentation.

Request an e-commerce demo →
Call me back