ERP-native product search

A sync layer is any process that copies catalog data from the ERP into a separate search database on a schedule. For a retail store with stable stock it is fine. For a distributor it causes four recurring problems:

• Stale stock. A product sells out at 10:05 and the storefront still shows it available until the next sync. The buyer orders, and someone has to call to cancel.
• Price mismatches. Tier and contract prices change in the ERP, but search results show the old price until the sync runs. Buyers then dispute invoices.
• Two product lists. Every new SKU, alias or barcode has to exist in both systems. Mistakes in mapping become zero-result searches.
• Hidden cost. Connector apps, integration platforms and the developer time to keep them working are rarely counted in the price of search.

Shopsense reads product, stock and price data from your ERP. No schema changes, no plugins installed inside the ERP, no write access. When an item, quantity or price list row changes, the affected index records are updated from that change. The exact method, whether an API, a read-only database login or change data capture, is confirmed for your ERP on the demo. Named ERPs are listed only after that confirmation.

Enterprise can connect more than one ERP. Each maps to its own catalog or warehouse set.

Shopsense indexes everything a buyer needs to find and choose a product, taken from the ERP as the single source of truth:

• Item code, manufacturer part number, UPC, EAN and any alias field you map
• Product name, description, brand, category and attributes such as flavour, strength, size or pack count
• Quantity on hand, backorder status and expected dates
• Price lists, customer tiers, contract prices and active promotions
• Customer assignments, so each account sees only the catalog and prices it is entitled to

Data that is not needed for search, such as payment details, cost prices or supplier records, is never read. Per-warehouse quantity is indexed when the ERP stores it and that split is confirmed for your catalog.

The number that matters is the time from an ERP change to the updated search result. This page does not publish a median until it is measured on a named catalog over a named period. Scheduled sync tools typically refresh every 15 minutes to 24 hours. A dated benchmark will replace this paragraph when the measurement exists.

Integration pages are linked from this table once each ERP has a published page.