How do I keep stock and prices up to date in the store?
The ERP publishes in your online store what you decide to show and keeps it up to date on its own: stock, prices and the catalogue. All of that is controlled from Digital channels → Online store, with the Sync and Publish changes buttons in the top bar and with the settings in the Settings tab. Every send is logged and can be looked up.
What does the ERP publish in the store and what doesn’t it?
The ERP publishes four things and each one goes separately. The web categories you have marked as published, with their name, their description and their order. The publishable items assigned to those categories, with their name, their description, their codes and their variants. The stock. And the prices.
It also publishes each item’s image (file or address, depending on what the record has; see Prepare the catalogue). It doesn’t publish customers or documents: those go the other way. It doesn’t change your store’s settings or its tax settings.
What goes in the opposite direction are the orders, which are explained in Receive the store orders.
How often does the store sync on its own?
The ERP works on its own, in the background, without anyone having the screen open. Each type of work has its own pace, which can be set per store in the Settings tab.
| Work | How often out of the box | Condition |
|---|---|---|
| Orders | 5 minutes | Always |
| Stock | 15 minutes | With Sync stock on |
| Prices | 15 minutes | With Sync prices on |
| Catalogue | 60 minutes | Only with Automatic publishing on |
If you shorten a pace and save, the change applies straight away: the next run is brought forward to what the new pace sets, without waiting for the one scheduled with the old one. If you lengthen it, the run already scheduled still happens, and from then on it follows the new pace.
None of this happens if the store isn’t active and already adopted. A deactivated store, or one waiting to be linked, stays still even if it has intervals set.
The full catalogue is the heaviest operation and that is why it comes turned off out of the box. Publishing the whole catalogue against the store of someone who hasn’t asked for it isn’t a service: it is an accident. While Automatic publishing is off, the catalogue only goes when you ask for it.
What is the difference between Sync and Publish changes?
They are two different buttons because they do two different jobs. Both are in the top bar of the online store screen.
Sync is the day-to-day job. It brings in new orders, converts them, and refreshes stock and prices. It doesn’t touch the catalogue: it doesn’t create or change products in the store.
Publish changes is the heavy job. It goes through the whole catalogue and publishes in the store whatever has changed since last time: new categories, new items, names, descriptions and variants.
If Publish changes creates new items in the store and Sync stock is on, it also sends their stock when it finishes. That way a new item shows its units from the start, instead of appearing out of stock (or hidden, if you do not show out-of-stock items) until the next sync. If you only changed items that were already in the store, there is no need: they already had their stock.
Rule of thumb: if you have changed prices or have sold, Sync. If you have changed the catalogue —categories, items, texts—, Publish changes.
How do I know a sync is running?
While a sync is working, a notice with a bar appears at the top. It shows across the whole ERP, not just in the online store: you will also see it if you are in the POS or on another screen. The notice says what it is doing, the percentage and which store it is (‘Store “My store”’). Click it and it takes you to the online store.
- Publish changes counts the entries: ‘Publishing changes to the store: 15 of 120’.
- Sync counts the steps (orders, order conversion, stock and prices), for example ‘Syncing with the store: prices · step 4 of 4’. It counts steps rather than entries because stock and prices go to the store in a single send.
The notice also shows when the store updates on its own, at its set frequency. Its text then starts with ‘Automatic’. While it lasts, Publish changes and Sync are greyed out and light up again on their own when it finishes. The notice disappears when it finishes.
Why are the Sync and Publish changes buttons greyed out?
Both buttons are greyed out when there is nothing to sync, and when you hover over them they tell you the exact reason: that no store is set up, that it is deactivated or that it hasn’t been adopted yet. They are also greyed out while a sync is running on that store.
Can I schedule the sync for a specific time?
Yes. Besides the intervals in the Settings tab, you can schedule the sync as one more ERP task, for example every night.
- Click Schedule…, in the top bar of the screen. Schedules opens with a New schedule already filled in: the name is ‘Sync the online store’ and the step is Sync store.
- Choose when it runs: at a clock time or when an event happens.
- Press Save.
The schedule is left Pending approval. It doesn’t run until someone with permission approves it in Schedules.
Exactly what stock is published?
The sum of the stock in the warehouses you choose for that store is published. They are chosen in Digital channels → Online store → Settings, on the store record, in the Warehouses that count towards the website stock section: tick one, several or All. Out of the box they all count, and if you untick the last one, they all count again. Each store has its own choice: you can publish the central warehouse stock on one website and the stock of all of them on another.
The change applies from the next stock sync; click Save on the record and, if you don’t want to wait, Sync.
If the sum comes out negative (more has been sold than was recorded, or the data comes unbalanced from an import), 0 reaches the store: for the buyer that means ‘none left’. The negative stays in the ERP, where it has to be sorted out.
For items with sizes and colours, each variant keeps its own stock. The store receives the stock of each size and each colour, which is how it sells them. An item without variants publishes a single figure.
Stock is only published for what is already linked with the store. An item that hasn’t been published yet has no place in the store to write its stock, so it is skipped.
What happens if someone deletes a product from the store?
The ERP notices in the next sync: the store tells it that product no longer exists. From that moment it stops sending it stock and price —it doesn’t come up as an error again and again— and, out of the box, it doesn’t publish it again: if someone deleted it in the store, it is assumed to be on purpose.
You will see it on the store record (Settings), in a yellow Deleted in the store box, with the list of products. If you want one to come back, click Publish again on its row: it will appear in the store on the next Publish changes.
If you prefer the ERP to always recreate them without asking, turn on Recreate products deleted in the store, in the sync section of the record.
What price is published?
The sales price the ERP has for that item is published, excluding VAT. If a variant has its own price, its own is published; if not, it inherits the item’s.
The store adds the VAT, with the tax rule it has set up for each product. That is why it matters that the store is set up to enter prices excluding taxes.
If your WooCommerce or Shopify store is set up the other way round —with prices including taxes—, that case isn’t supported and the store will undercharge. The ERP detects it and leaves a visible warning in the log. It is explained in Connect my online store.
In PrestaShop, if the VAT rate mapping hasn’t been set up, new items are created with the store’s default tax group and a warning is left saying so.
Why isn’t a change I have just made being published?
The ERP publishes only what has changed. In each catalogue publication it compares the content of each item and each category with what it sent last time, and skips everything that is still the same.
That is what stops publishing a large catalogue from taking forever or hammering the store with thousands of useless writes. It also means that clicking Publish changes twice in a row does no work the second time.
If you have changed something and it doesn’t get there, check three things in this order. That the category is Published and not Draft or Hidden. That the item is marked as Publish in the online store on its record. And that the item is assigned to some published category.
Price and stock changes don’t need Publish changes: they go with Sync, which is much faster.
Where do I see whether the sync went well?
There are two places, from less to more detail.
Under the screen header, after starting a sync by hand, a strip appears with a summary of what it has done. For example ‘Orders: 3/3 · Conversion: 3/3 · Stock: 120/120 · Prices: 120/120’. If there were failures, the strip is highlighted and says how many.
The full log, including the syncs the ERP does on its own, is in the Settings tab: open the store record and look at the Latest syncs card at the side. It is explained in the next section.
What does the Latest syncs panel tell me?
It is a timeline with each run for that store, from most recent to oldest. It is at the side of the store record, in the Settings tab. It shows every run: the ones you start and the ones the ERP does on its own, whether they went well or had errors.
Each run says, from top to bottom:
- How long ago it was: ‘a few seconds ago’, ‘1 min ago’… Hover over it to see the exact date and time.
- What it was and who started it: Catalogue, Stock, Prices, Orders, Conversion or Adoption, followed by the origin. For example ‘Stock · Scheduled’ is a run the ERP did on its own, at its set frequency.
- How many entries went out of how many, for example ‘13/18’.
- If there were failures, a red label saying how many: ‘5 with errors’.
- How long it took, in seconds (‘9 s’). If it says in progress instead, it is a job that hasn’t finished yet, or one that was cut off halfway.
The dot on the left of each run is grey if it finished cleanly, red if it left errors and blue while it is still running.
When there is more information, the details link appears. Clicking it expands the list of what was published and what failed, with the reason for each failure; Hide detail folds it again. That is where you see the warnings: the tax ones, those for images that couldn’t be published and the products the store rejected.
Only the latest runs are kept. When the list is full, the footer says so.
If it has never synced, the panel says ‘This store has no recorded runs yet.’.
What happens if something fails halfway through a publication?
In the catalogue publication, an item that fails doesn’t stop the rest. It is noted with its cause and the publication carries on with the others. When it finishes, the summary says how many went out and how many failed.
What was already published stays published, even if the publication is cut off afterwards. The next time the ERP updates those products instead of creating them again: nothing is ever duplicated in the store.
Stock and prices work differently, because they go in a single send. If that send fails, nothing from that batch is published and the log says so. The next sync tries it again in full.
Can I start two syncs at the same time?
Not on the same store. There is only one job at a time per store, and it doesn’t matter whether the ERP asks for it on its own or you ask for it with a button. If you try to start another, it tells you: ‘A sync is already in progress for this store. Wait for it to finish.’
With several stores there is no problem. Two different stores sync at the same time without getting in each other’s way.
While your sync is running, the bar buttons are greyed out and the notice says there is one in progress. When it finishes they light up again, and the run appears in Latest syncs.
If something goes wrong
The tabs mentioned are in Digital channels → Online store.
| What you see | What has happened | What to do |
|---|---|---|
| ‘There is no store configured.’ | No store has been added | Create it in the Settings tab |
| ‘Store “…” is disabled.’ | Active store is turned off | Turn it on in the Settings tab |
| ‘Store “…” has not been adopted yet: run the reconciliation in the Adoption tab.’ | The store hasn’t been linked with the catalogue yet | Do the adoption before publishing |
| ‘Adoption pending: the store is not empty (… remote items) …’ | You are trying to publish to a store with products, without adopting | Finish the adoption and publish again |
| ‘A sync is already in progress for this store. Wait for it to finish.’ | Another job is keeping the store busy | Wait a few minutes |
| ‘The … connector does not support the … capability.’ | That platform doesn’t offer that type of send | Check with whoever is implementing the ERP |
| ‘The store declares “prices include tax” and the connector does NOT support it in this phase …’ | The WooCommerce store expects prices including VAT | Change the store to prices excluding taxes, or it will undercharge |
| ‘The store declares “all prices include taxes” and the connector does NOT support it in this phase …’ | The same in Shopify | Turn that option off in Shopify’s taxes |
| ‘No image: “…” of product … arrives with no content or public URL …’ | The item’s Image field is empty or points to a file that no longer exists | Put an image URL or an ERP attachment on the item record |
| ‘No image: “…” … there is no WordPress Application Password …’ | The WooCommerce store can’t receive the file without that key | Set up WordPress user and Application password in the Settings tab (or use a public URL) |
| ‘No image: “…” … is larger than 8 MB …’ | The photo is too big to publish | Reduce the file (8 MB maximum) |
| ‘Price not published on product …: it has … variants in the store and in Shopify the price lives on each variant …’ | The product has variants in Shopify that the ERP doesn’t control | Link those variants with the adoption |
| ‘Item “…” is created with the store’s default tax group: no VAT mapping is set up …’ | The VAT hasn’t been set up in the PrestaShop options | Ask for the tax mapping to be set up |
| ‘Inventory written to location … the store’s first active one …’ | Shopify has several locations and it hasn’t been said which one to use | On the store record, press Read locations and choose the right one |
| ‘The WooCommerce store does not use HTTPS: Basic authentication with ck/cs travels in clear text.’ | The store address starts with http:// | Put the store on https:// and correct the address |
| In Latest syncs a run has the red label ‘… with errors’ | Some entries couldn’t be sent | Click details on that run and read the reason for each failure |
| I publish and nothing changes in the store | The ERP only publishes what has changed | Check that the category is Published and the item is marked Publish in the online store |
| The website stock doesn’t match the ERP’s | That item isn’t linked with the store, or the send failed | Check the log of the last Stock sync |
See also: Connect my online store · Prepare the store catalogue · Receive the store orders
More about Online shop
- How do I view and prepare my online store’s receipts?
- How do I show colours and materials with a photo instead of their name?
- How do I connect my online store to the ERP?
- How do I link a store that already has products?
- Selling online with the ERP behind you
- Who are the customers who buy on the website?
- How do I prepare my online store’s catalogue?
- How do I receive the orders from my online store?