ERP-integrated ecommerce search: how it works and why sync fails

Most search tools never touch the ERP. They index a product feed from the ecommerce platform, which was itself populated from the ERP by a connector. The chain usually looks like this:

1. The ERP holds items, quantities and price lists.
2. A connector or integration platform copies that data into the ecommerce platform every 15 minutes, hourly or nightly.
3. The ecommerce platform pushes a product feed to the search vendor, on its own schedule.
4. The search vendor indexes its copy and serves results.

Each hop is a point where the storefront and the ERP can disagree. By the time a buyer sees a result, the stock quantity may have passed through three systems and two schedules.

A sync layer fails a distributor because the data that matters most, stock and price, changes faster than any sync schedule. Retailers with stable inventory tolerate the delay. Distributors see four recurring problems.

• Stale stock. An item sells out at 10:05. The storefront shows it available until the next sync. A retailer orders it, and someone has to call to cancel the line.
• Price drift. A tier price changes in the ERP on Monday. Search results show the old price until the connector runs. The buyer's invoice does not match the price they saw, and a dispute follows.
• Two product lists to maintain. Every new SKU, alias and barcode must exist in the ERP and in the synced copy. A mapping error in either place becomes a zero-result search.
• Hidden cost. The connector licence, the integration platform and the developer hours spent fixing failed syncs are real costs of search that never appear on the search vendor's invoice.

The guide to real-time inventory and pricing covers what buyers experience when these failures reach the result list.

ERP-native search means the search index is built directly from the ERP's item, inventory and price list tables, with no intermediate copy owned by another system. When a value changes in the ERP, the index updates from that change. There is one product list, one stock figure and one price per account, and all of them belong to the ERP.

Shopsense is a B2B ecommerce search engine for distributors and wholesalers that connects directly to ERP systems. It reads with read-only access and updates the affected index records from the ERP change. The connection method and a measured latency are published when they are confirmed for a named ERP. A dated benchmark is the proof this page is waiting on.

An ERP-native index should hold everything a buyer needs to find and choose a product, and nothing else. Reading too little produces weak search. Reading too much creates a security review for no benefit.

Include:

• Item code, manufacturer part number, UPC, EAN and every alias field.
• Name, description, brand, category and attributes such as flavour, strength, size and pack count.
• Quantity on hand, per warehouse where the ERP tracks it, plus backorder status and expected dates.
• Price lists, customer tiers, contract prices and active promotions.
• Customer assignments and product restrictions, so each account sees only what it may buy.

Exclude:

• Payment details, credit limits and terms.
• Cost prices and supplier records.
• Any personal data about the buyer's staff beyond the account identifier.

Any vendor connecting to your ERP should answer five questions in writing before you grant access. The answers belong on their security page. Shopsense does not link a security page here until that page exists.

1. Is access read-only, and how is that enforced?
2. Which tables or endpoints are read, and which are never read?
3. Where is the index hosted, and in which region?
4. How is data encrypted in transit and at rest?
5. What happens to the index and credentials when the contract ends?

The single number that matters in ERP-integrated search is the time from a change in the ERP to that change appearing in a search result. Vendors rarely publish it. Ask for it, and measure it yourself during a pilot.

A fair method: change the quantity of 50 items in the ERP at known times, query each one every second, and record when the new value appears. Report the median and the 95th percentile, the catalog size and the test period. Shopsense will publish that result on this page when the test has been run.