WooCommerce

The store you already run still has to agree with the marketplaces.

WooCommerce is the storefront the brand already operates. Orders, catalog, and stock live there first. They still have to agree with every marketplace on one record: the same SKU, a price inside the band, a quantity that matches.

What Unison reads

The store's own orders, catalog, inventory, and payouts.

Someone on the team already lives in this store. A weekend of sales changes on-hand stock. A price edited on Thursday has to show up on the marketplaces that sell the same SKU. Unison reads the store into the one record those channels share.

Orders the store already took, so last month on WooCommerce is revenue and the change, back in seconds.
Catalog as the store holds it, SKU by SKU, including a product a marketplace is missing.
Inventory on hand, with days of cover that count the store's own pace.
Payouts the store settled, read beside what each marketplace paid.
WooCommerce · on the record
orders · the sales the site already took
catalog · SKUs the marketplaces have to meet
inventory · on hand · days of cover
payouts · what the store settled
charts from those four
forecast · restock and revenue
What a write looks like

The store moves when the record moves.

A write on WooCommerce is a launch, a price, a quantity, or a rewrite of the product the store shows. Each one stays inside the band, and each one ends as publish, wait, or block.

Launch

A SKU the store is missing.

When the marketplaces already sell a product and WooCommerce is missing it, the launch puts the listing, the price, and the stock on the store together. When the store has the SKU and a marketplace is missing it, that launch leaves from this same record.

Price and stock

A change inside the band.

The store's price or quantity updates with the marketplaces, inside the band you set. A Friday edit in the store and a Friday edit on a listing become one write, so the catalog the brand already trusts stays the catalog the channels sell.

Listing

Copy rewritten for the store.

The product description can be rewritten for WooCommerce: the title and the body the storefront shows, drawn from the brand's own catalog. The marketplace listing and the store page can say the same product in the fields each one uses.

Guardrails

Publish, wait, or block.

A store write inside the band can publish. A product page you want a person to read can wait. A price or a stock change that leaves the band is blocked. The leash sits on the store the same way it sits on every marketplace.

Last month and a launch

The product shows this example. The store is $8,640, up 4.2%.

The product film shows an example month. WooCommerce comes back with the other marketplaces, revenue and the change, in seconds. In that example the store is $8,640, up 4.2%.

Charts under that line are built from the store's orders, catalog, inventory, and payouts. A restock forecast and a revenue forecast sit on the same read, days of cover included, so a quieter month still names the SKUs the store is about to run short of.

A launch in the product is the Aurora Candle when WooCommerce is missing it. Listing, price, and stock arrive on the store together. An answer about what sold, on the store or beside it, comes from the brand's own orders, ads, and catalog.

Example month · the product
WooCommerce $8,640 +4.2%
revenue and the change · seconds
Launch · Aurora Candle
missing from the store · listing, price, stock
Forecast · days of cover
restock and revenue, from the store's orders
What the call asks

Is the store live, who holds the login, and does it have a clean API.

WooCommerce is usually already running. The call still starts by naming it, because the catalog on the store is the one the marketplaces have to meet. We ask three things before any write is in scope.

Which channels are live

WooCommerce, and the marketplaces beside it: Amazon, Walmart, Faire, Shopify, eBay, Etsy, TikTok Shop, and any other storefront already selling. Planned channels count too, so a launch has somewhere to go.

Who holds the login

The person who can open the store today. That might be someone on the brand, a developer, or an agency. The read and the write both need that login in the right hands.

Whether it has a clean API

We ask whether WooCommerce has a clean API, in plain language. The answer decides how orders, catalog, inventory, payouts, and writes connect. We name the channel. We leave product names for APIs off the call.

What may publish, wait, or block

Which store changes can publish on their own, which wait for a person, and which are blocked outside the band. Price, stock, and a new product page can each have a different rule.

The other marketplaces

The store is one row. These channels share it.

A SKU edited in WooCommerce is the same product on every marketplace below. The way that record is connected, unified, and written back is on the platform.

See how the platform holds the record
The store and the marketplaces

Bring the store you already run.

We'll look at which channels are live, who holds the WooCommerce login, and whether that channel has a clean API. Then we'll say what the first write on the store would be.

Schedule a call