Who this is for
Owner or manager of a Magento 2 or Adobe Commerce store whose admin edits to products, prices or stock take a long time to show, or never show, on the storefront.
You changed a price, stock level or product and the site still shows the old data hours or days later, or products have gone missing from category pages.
The result
On a copy of your store, an edit to a test product appears on the storefront within the agreed time, every indexer is in the agreed mode and status, and the scheduled job that keeps them current is shown completing.
What is included
- The status and update mode of each indexer, and whether any are suspended or invalid
- The scheduled jobs that apply index changes: whether they run, finish and succeed
- The change-log tables and the database triggers that feed them
- A test product edit followed to the storefront, with the corrected settings or schedule written down
You receive
- A table of indexers with mode and status before and after
- A note naming why edits were not showing, with redacted command and job evidence
- The corrected indexer modes and the scheduled-job change your host must make
- A test record: test edit, time made, time visible on the storefront
- Steps to apply the changes to the live store, including maintenance mode, and to undo them
What is not included
- Search engine, caching layer or content delivery network faults, beyond ruling them out
- Slow storefront performance and server sizing
- Extension code that writes data incorrectly
- Repairing wrong product data that was entered in the admin
- Upgrading Magento or Adobe Commerce
What we need from you first
- What changed and where it fails to show: price, stock, product or category
- How long the storefront lags, and whether a manual reindex fixes it
- The Magento or Adobe Commerce version and host type, if known
- Whether indexers are set to update on save or on schedule
- Whether anything changed recently: upgrade, migration, host move or extension
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- Every indexer on staging is in the agreed update mode and none is invalid or suspended
- The scheduled job that applies index changes shows recent runs that completed successfully, with none stuck pending
- A test product price edit on staging appears on its storefront page within the agreed time
- A test stock change appears in a category listing within the agreed time
You review the evidence and the staging test and sign off before payment. Applying the change on live, in a maintenance window, is a separate step your host takes.
When we would stop or decline
- The data is wrong in the admin as well, so reindexing would not help
- The scheduled jobs cannot be changed by you or your host
- The staging copy cannot reproduce the fault because it has little data
- A full-page cache or content delivery network is the cause and its configuration is not available to us
Questions
Do you need access to my live Magento server?
No. We work on a staging copy, and your host or developer runs any command on live.
Why does a manual reindex only help for a while?
A manual reindex runs once. If the recurring job is not keeping up, the same lag returns, which is what we trace.
Will the fix work on every Magento version?
We state the version we test against. Behaviour such as the customer grid indexer differs between 2.4 releases, and we say where it matters.
Price and terms
From £495 · untested offer price. After the agreed checks pass and you sign off; no payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.