Edit a product — what actually reaches the channels
Your PATCH always updates Nembol; what propagates to each channel is governed by the seller's sync settings.
PATCH /products/{id} (and the variant/inventory endpoints) always update
Nembol — synchronously, and the response reflects it. Whether the change
then reaches each channel is a different question, governed by the
seller's per-channel sync settings in the Nembol dashboard.
The "Sync product edits" switch (per channel)
Every channel connection has a Sync product edits setting. When a listing's channel has it:
- ON — the edit propagates fully: content, price and quantity are pushed to the channel.
- OFF — Nembol pushes only the quantity (the channel keeps its own content and price; minor per-channel nuances: OnBuy still pushes price+stock, Google Merchant Center only availability).
This is a seller choice, not an error: many merchants curate content directly on a channel and use Nembol for stock only.
Why this matters to your integration
You can PATCH a title, get a 200, watch the operation succeed — and
still see the old title on the channel, because the job legitimately pushed
quantity only. If a content edit "didn't take" on one channel:
- Don't retry — the API did exactly what the seller configured.
- Ask the merchant to check Channels → (channel) → Sync product edits in their dashboard.
- Once enabled, force a re-push with
PATCH /listings/{id}and an empty body (a plain re-sync).
Edits can also flow the other way
Sellers can elect one channel (Shopify or WooCommerce) as their content leader: edits made on that channel flow into Nembol — and from there to the other channels. If that's on, content your integration writes can be legitimately overwritten by the seller's channel-side edits. For stock, channel-side quantity edits and sales flow into Nembol according to their own per-channel switches.
Rule of thumb: Nembol is the hub, but the seller decides the direction of each pipe. If your integration assumes it's the only writer, agree with the merchant on which switches stay off.
Gotchas
- Prices can be transformed on the way out — per-channel price rules (percentage/fixed adjustments) apply when pushing, so the channel price differing from your PATCH is expected when rules are set.
- Quantity always syncs (it's the one thing every mode pushes) — if
even quantity doesn't move, that's a real error: check the listing's
issues[]and the operation. - These settings are per channel account — one eBay account can be full-sync while a second one is quantity-only.
Read the switches from the API
You don't have to ask the merchant: every entry of
GET /channel_accounts carries the
switches read-only —
{
"id": "chac_66a1f09b2",
"channel": "ebay",
"sync": {
// Nembol pushes content + price + quantity to this channel.
// false = quantity only — the channel keeps its own content and
// price (two exceptions: OnBuy still gets price+stock, Google
// Merchant Center only availability).
"product_edits": true,
// Sales on this channel adjust stock everywhere.
"quantity_from_orders": true,
// Quantity edited directly ON the channel flows back into Nembol.
// null = the seller never set it; the channel's default applies.
"quantity_from_channel_edits": null,
// true would make this channel the CONTENT LEADER: its edits
// overwrite Nembol content (at most one channel per store).
"content_from_channel_edits": null
},
// Price rule applied when Nembol pushes prices to this channel:
// here every price goes out +10%. This is why the channel price can
// legitimately differ from what you PATCH.
"pricing": {"mode": "percentage", "value": 10},
// Stock buffer: the channel shows the product IN STOCK only while
// quantity >= 100. A variant with 50 units on hand is deliberately
// shown as out of stock on this channel.
"inventory": {"control": true, "threshold": 100}
}Changing them stays in the seller's dashboard on purpose: they encode who owns a channel's content, and that's the merchant's call. Field-by-field details in the Channel account model.
Last updated on July 30, 2026
Need help?
The API is in private beta — email us and a human replies, usually within one business day.