eCommerce Sites

Last updated: June 20, 2026

The eCommerce integration connects your online stores to Cloudby, pulling their orders in and pushing your stock out, so a sale on the web becomes a retail order here and your inventory stays in step across every channel. It is a genuine, scheduled two-way sync, not a manual export.

What you will learn
  • Which platforms are supported
  • How the two-way sync works
  • Why product mapping matters
  • How an online sale posts to the accounts
Online storeWooCommerce / ShopeeCloudbyretail orders + stockorders in (ingress)stock out (egress)A scheduled two-way sync: store orders flow in, your stock levels flow back out
A scheduled two-way sync ties an online store to Cloudby simplified mockup

Anatomy of the screen

An eCommerce site has tabs for the store itself, the Integration (the API connection), Automation (the fulfilment flow triggers), Mapping (tying store products to your stock), and Tools (sync utilities). The supported platforms are WooCommerce and Shopee.

How it behaves

Two-way scheduled sync

A background schedule runs the sync in both directions: orders flow in (ingress) on one cadence and your inventory pushes out (egress) on another, so the store reflects your real stock and you never miss an order. Each order carries its own sync state with error and retry handling, so a single failed order can be diagnosed and re-run without holding up the rest.

Mapping is essential

The integration only works if the store's products and SKUs are mapped to your inventory stock items. That mapping is what lets an incoming order's lines land on the right stock and an outgoing stock update reach the right listing. Get the mapping right and everything else follows.

Posting an online sale

An eCommerce site carries dedicated ledgers, for platform fees, customer payment, delivery, sales revenue, discount and tax, so an online sale posts to the accounts correctly, with marketplace commissions and gateway fees landing where they belong rather than muddying revenue.

Worked example

You connect your WooCommerce store, map its catalogue to your SKUs, and set the sync running. Orders now arrive automatically as retail orders, your stock levels push back to the storefront so it never oversells, and each sale posts revenue, fees and tax to their ledgers.

Edge cases and good practice

  • Map before you sync. Unmapped products cannot land on the right stock.
  • Watch the per-order sync errors; they isolate a problem order without stopping the feed.
  • Wire the channel ledgers so fees and commissions do not distort revenue.

Related