Automation · Marketplaces

Keep WooCommerce price and stock up to date on Homecenter

An AI agent carries price with the channel margin and buffered stock from your WooCommerce store to Homecenter, by SKU and with no double entry.

Show me this with my own operation See every automation

How do I keep my store's price and stock up to date on Homecenter without entering them twice?

A scheduled task reads price and stock from your WooCommerce store, which is the single source of truth, and for variable products it takes each variation with its own SKU. It applies the channel margin and the stock buffer you define, checks that the SKU exists on Homecenter and writes the already calculated values to Seller Center. If a product sold out, it publishes zero units so you do not sell what you do not have. It then reviews the marketplace's recent orders and, if the team says none are coming in, checks the notifications Homecenter sent instead of guessing where the chain broke. It does not list new products: it updates the ones already there.

Where it applies: Colombia. Homecenter operates in Colombia on Falabella's Seller Center, and this procedure signs every call with that platform's protocol.

What starts it

At a set time

A task with a recurring trigger, for example once or twice a day, goes through the store products you sell on Homecenter. It can also run for a single SKU when a price changes and you do not want to wait for the next run.

A task on a recurring (cron) or date and time trigger. It runs on its own, with nobody logged in.

Who runs it

Igor, Warehouse manager

This is the recurring half of his job: the store leads and Homecenter is the destination. Igor writes the values the task already calculated with your margin and your buffer, and does not invent prices or quantities when a store figure is missing.

Run by the marketplaces Met

What you need connected

Homecenter Run stores and orders
WooCommerce Run stores and orders

6 steps · 7 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Read price and stock in the store

The task searches WooCommerce for the products you sell on the marketplace, by SKU or by category, and reads their price and available units. For a single product it opens the full record. The store is the only source: anything someone changes by hand on Homecenter is replaced on the next run.
- wc_list_products WooCommerce
- wc_get_product WooCommerce
2
Take each variation with its SKU

In a WooCommerce variable product the SKU is not on the parent product: it is on each variation, such as size or pack, with its own price and stock. The task lists the variations and handles each one separately, with the SKU it already has, without creating a new one.
- wc_get_variations WooCommerce
3
Check that the SKU exists on Homecenter

Before writing, the Met looks the product up on Homecenter by the same SKU as the store. That search accepts partial matches and returns a single result, so the Met compares the SKU that came back with the store's and does not write if they differ. If it is not there, it does not create it: it flags that the product needs a marketplace listing, which goes through Homecenter's validation and is not instant.
- homecenter_get_product_by_sku Homecenter
4
Write the channel price and the buffered stock

The task calculates the price with the channel margin and the stock with the safety buffer, and the Met writes those values to Homecenter, by SKU. It can send both or only the one that changed: if only stock dropped, the price stays as it was. When the product sold out in the store, it publishes zero units. It is worth running a single test SKU first and checking it in Seller Center before releasing the whole catalog.
- homecenter_update_price_stock Homecenter
5
Review the marketplace's recent orders

The Met lists Homecenter's recent orders, filtering by status when you ask, for example the pending ones. Each order carries its number, status, date, total, currency, how many items it holds and the customer's name. It does not carry the lines with their SKUs, so this list tells you what needs shipping, not which products to deduct.
- homecenter_get_orders Homecenter
6
Diagnose when orders are not arriving

If the team says no orders are coming in, the Met reviews the latest notifications Homecenter sent to your workspace, with arrival time, signature check and the processing error if there was one. Not every Seller Center account has notifications enabled: in that case the order query is the way, and the Met says so.
- homecenter_list_recent_events Homecenter

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Seller Center API host, seller identifier and API key

Homecenter assigns the host when it enables you as a seller with API access. The identifier is usually your seller account email, and the key comes from the Seller Center settings; it signs every call and is stored encrypted per workspace.
Your WooCommerce store connected

With your store's REST API keys. It is the source of truth for price and stock: without it there is nothing to sync against.
The channel margin and the stock buffer

You define them when building the task: how much the price goes up on Homecenter and what share of stock is not published. The Met does not decide them, it applies them.
The same SKU in the store and on Homecenter

Matching is by SKU, the marketplace SellerSku. A different SKU breaks nothing, but that product is not found and the Met reports it separately.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not create products in the Homecenter catalog. It updates price and stock of products that already exist there; listing a new one goes through the marketplace's validation.
It does not accept, reject or ship orders. It lists them for review; logistics stays where it already is.
It does not deduct Homecenter sales from the store. The order list does not carry lines with their SKUs, so there is nothing to deduct with from this procedure.
It is not real time. There can be a gap of hours between two runs, and the stock buffer exists precisely to absorb it.
It does not validate the signature of an order notification if Homecenter provides no secret. In that case the notification is still recorded, without verifying its origin.
It has not been tested against the real Homecenter instance. The connector was built from the Seller Center documentation, without Homecenter credentials, and the format of the price and stock update and of its notifications is still to be confirmed. That is why it is worth starting with a test SKU and checking it in Seller Center.

FAQ

Questions about this automation

Because the task applies the channel margin you defined before writing it. The Met receives the value already calculated and publishes it as is; it does not round or adjust on its own.

Each variation syncs separately, with the SKU, price and stock it has in WooCommerce. The parent product has no SKU of its own, so it is not used for matching.

No. This procedure keeps price and stock for products already in the marketplace catalog. Listing a new product follows Homecenter's process.

Because the Homecenter marketplace runs on that platform. The connector signs every call with its protocol, which is what answers on the other side.

Keep going