A channel strategy built on one commerce core
Multi-channel Selling lets the same product, stock, and order data travel to every place you sell — Meta, Google, TikTok, a marketplace — instead of each channel keeping its own separate, drifting copy.
Multi-channel Selling lets the same product, stock, and order data travel to every place you sell — Meta, Google, TikTok, a marketplace — instead of each channel keeping its own separate, drifting copy.
As soon as a business sells through more than one surface, keeping everything lined up becomes a real cost. Products drift, channel listings go stale, and order states become difficult to trust.
Publishing your catalog outward to marketing channels and pulling sales orders inward from a marketplace are two different jobs, so they're built and kept separate on purpose — one never gets confused for the other.
If product identity, stock counts, or order tracking are vague to begin with, the problems show up fast the moment a merchant expands beyond their main storefront.
Good multi-channel architecture needs to handle both publishing products outward and receiving sales inward, without confusing the two or treating them as the same problem.
Meta, Google, and TikTok all accept your catalog through a real-time push, so they're handled the same way. Pinterest works differently — it reads from a hosted feed file on its own schedule — so it's built to match how Pinterest actually works, not forced into the same shape as the others.
Every product (or size/color variant) keeps one permanent identity across every channel, so a listing on Meta or Google always maps back to the exact right item — never a renamed or mismatched one.
Merchant impact: Listings stay more consistent across destinations as the catalog changes.
Developer impact: Integrations have a durable product identifier rather than guessing from mutable titles or SKUs.
Example: A product variant maps into a catalog feed with a stable channel-facing identity instead of collapsing several sellable offers into one ambiguous listing.
Meta, Google, and TikTok are connected and synced automatically. Pinterest works differently, so instead of a connection, you get a feed link to paste into Pinterest's own settings — matching how Pinterest actually works.
Merchant impact: Operators can manage destination readiness more clearly, and see exactly which destinations are "connect and sync" versus "copy this feed URL."
Developer impact: Meta's Catalog Batch API, Google's Content API `products.custombatch`, and TikTok Business API's Catalog Management batch-update endpoint share one push-based `CatalogProvider` registry with a daily scheduled sweep (`api/cron/sync-catalogs`). Pinterest is a separate, pull-based feed (`api/public/catalog-feed/[storeId]/pinterest`).
Example: A brand pushes products to Meta and Google through an API-driven batch sync while Pinterest reads the hosted feed file on its own schedule.
A sale from a marketplace shows up in the same order system as a storefront sale — never duplicated, never lost, and never left sitting in a spreadsheet somewhere else.
Merchant impact: Cross-channel selling becomes operationally real, because order truth flows back into the same platform instead of living in a spreadsheet.
Developer impact: `Order.channelOrigin` (`{channel, externalOrderId}`) is the idempotency key for every inbound channel order. Every line item resolves through a `ChannelProductMapping` before it touches `StoreProduct`; an unmapped line fails the whole import closed rather than creating a partial, half-tracked order.
Example: The `manual` channel is a reference implementation (no real marketplace credentials needed) used to exercise the whole inbound pipeline end to end; Amazon, Flipkart, and Instagram are on the connection roadmap, each getting its own dedicated adapter.
A sale on a marketplace updates the same stock count your storefront reads from — because that sale already happened whether or not Prebit's own count agrees, so it's reflected immediately rather than getting stuck or blocked.
Merchant impact: Customers stop seeing different prices or availability depending on where they find the product.
Developer impact: One backend model serves more than one frontend and destination, with no separate inventory code path for channel-originated orders.
Example: A limited-stock item becomes unavailable on the storefront and across downstream destinations instead of lingering as purchasable in one place.
Every layer feeds the next: Multi-channel Selling sits inside this chain rather than bypassing Commerce Engine's data contracts.
Products, offers, and stock state originate from the shared commerce core, keyed by `catalogItemId`.
Push-based providers (Meta, Google Merchant, TikTok) share a `CatalogProvider` registry and a daily sweep cron; Pinterest is a separate, pull-based public feed URL.
`importOrder.ts`/`importRefund.ts` map channel payloads into Prebit's own order, refund, and stock logic, idempotent by `{channel, externalOrderId}`.
Merchants see publication health and channel state under Settings → Sales channels while the main storefront stays aligned with the same backend truth.
Product information and availability stay more consistent as the business expands outward.
Teams spend less time fixing channel mismatches manually after sales or catalog updates.
A cleaner backend makes future channel launches less chaotic — the manual channel proves the inbound pipeline works before a real marketplace adapter has to be written.
Cross-channel activity becomes easier to understand when incoming and outgoing flows share one system.
Each destination or sales channel transforms the canonical model without redefining it — `CatalogProvider` for outbound, `SalesChannelConnection` for inbound, never merged into one shape.
Web, feed, and import workflows speak the same backend language via `catalogItemId` and `channelOrigin`.
Amazon's Selling Partner API — LWA refresh-token OAuth, AWS SigV4-signed requests, and a multi-step Feeds API document-upload flow — gets its own purpose-built design rather than being squeezed into a generic adapter shape that wouldn't do it justice.
Future adapters land on top of a stronger catalog and event base rather than on top of storefront shortcuts.
A brand wants to sell from the main storefront while also publishing to Meta, Google, TikTok, and Pinterest catalog destinations.
Outcome: More reach without throwing product truth into disarray.
An agency builds multi-surface go-to-market setups for clients with growing channel ambitions.
Outcome: Fewer brittle channel-specific workarounds at launch time.
A merchant wants channel orders reflected back into the main operating system, starting with the manual channel as a stand-in until a real marketplace adapter exists.
Outcome: Better stock and order visibility across the business.
A platform team needs to add destinations over time without rebuilding the catalog model each time.
Outcome: Better scalability of channel work.
Channel expansion becomes cheaper when the same product identity and inventory model power several surfaces.
Operators lose less time reconciling channel discrepancies after the fact.
Feed publication and order import benefit from explicit lifecycle handling — a daily sweep cron for push feeds, a hosted TSV for pull feeds — rather than one generic sync job pretending both are the same problem.
The right foundation helps the business add surfaces without paying a systems penalty every time.
The same product truth can support storefront SEO work and downstream catalog visibility more coherently.
Stable offer identity improves how products can be represented across feeds and destinations.
Multi-channel expansion works best when landing pages, product pages, and destination surfaces all stay aligned.
Consistent product data and destination coverage can improve how clearly the business presents product truth across the web.
A direct, factual read on where each platform is strong, and where Prebit takes a different approach.
Directional and factual. Validate against your own catalog complexity, channel strategy, and budget before deciding.
Plain answers to what merchants, agencies, and developers actually ask.
Start free. No credit card required. Explore the rest of the Prebit platform once you're in.