Pushing products - single, bulk and updates

Pushing products - single, bulk and updates

Getting products to the 3PL

One at a time. Add a line on the Products page, pick product and instance, press the line's Push button.

In bulk. Add in Bulk opens a two-step wizard: step 1 is the standard Odoo product search (filter, group, tick individually or select all matching) - service products are excluded automatically; step 2 chooses the instance and the starting state:

  • To Push (send later or via Push) - lines are created queued.
  • Already at the 3PL (map only, no push) - lines are created as Synced; use this when onboarding an existing catalogue you know is already in the warehouse's system.
  • Push Immediately - tick to queue the whole selection for background pushing right away. Pushing runs in batches in the background precisely so that adding 500 products does not freeze your screen for minutes; lines flip from "Queued" to Synced/Error as they complete and every push is Sync-Logged.

Products already bound to that instance are skipped and reported, so running the wizard twice cannot create duplicates.

Push Queued Products (Products page > Perform Operation). Queues every To Push / Error binding of the chosen instance for the background pusher - the "catch up now" button.

Push Update on synced products. Products change - price, name, customs data. The Push Update button on a synced line re-sends the product's current Odoo data as an update (the connector knows to call the 3PL's update operation rather than create). Bulk-select lines and use the Push / Update at 3PL action to refresh many at once.

What a push sends

SKU, name, price and cost value, barcode where the provider takes one, weight (Sprint expects integer grams - the connector converts), and customs data: HS code and country of origin from the product form travel with every create and update, so customs-relevant edits in Odoo propagate by pressing Push Update.

The connector checks whether the SKU already exists at the 3PL before creating, so a push against an existing SKU becomes an update rather than a duplicate-product error.

    • Related Articles

    • Match Products - linking an existing catalogue

      Match Products - linking an existing catalogue For a 3PL that already holds your catalogue, Match Products (Products page > Perform Operation, or the button on the instance) pulls the 3PL's full item list and auto-matches it to Odoo products by SKU ...
    • How FBM stock reaches Amazon

      "I changed the stock in Shopify, so why has Amazon not updated?" is one of the questions we are asked most often. This article explains exactly when your merchant-fulfilled (FBM) stock is pushed to Amazon, so you can tell the difference between a ...
    • Choosing what to sync and how often

      What to sync Each switch enables one scheduled flow. Turning a switch off never deletes anything - it only stops the scheduler running that flow; manual runs from the Operations pages remain possible. Sync Orders (default on). Enables the two order ...
    • Roles and permissions

      Access to the connector is controlled by a single role picker on each user (Settings > Users > 3PL Connector): Read Only, Ops or Admin. Each level includes everything below it, and every button in the app is role-aware - users simply do not see ...
    • Managing your plan

      You can change plan at any time from the Plans page. Upgrades are simple and take effect immediately. Downgrades take a little more care, because your existing setup may be bigger than the plan you are moving to. This page explains exactly what the ...