Epicor BisTrack integration for ecommerce

Stock publishes on a schedule you control - typically every 15 to 60 minutes depending on order volume and your acceptable oversell risk. Real-time sync is not feasible because BisTrack processes allocations asynchronously. Between refreshes, commerce shows the last-published inventory. If you need instant availability updates, you must implement a webhook or API callback from BisTrack when stock changes, which requires custom development.

Orders queue locally in commerce or a middleware layer. iWeb builds retry logic that resubmits orders to BisTrack at intervals until they are acknowledged or a deadline is reached. If the deadline passes without acknowledgement, support is alerted and can manually intervene. The shopper is notified of the delay via email.

Yes, if customer identity is passed to commerce and pricing is tagged by customer or customer group in BisTrack. iWeb maps BisTrack's pricing tiers and agreement rules to your storefront's pricing engine. If a customer does not match a specific agreement, the base price applies. Price recalculation happens at cart time.

BisTrack publishes customer credit limits to commerce. At checkout, commerce checks the order total against the cached credit limit and either allows or blocks the sale. The cache refreshes on a schedule you define. If you want real-time credit checks, BisTrack must expose a synchronous API query, which may require additional BisTrack configuration.

Each order line in commerce is tagged with a product code that maps to a BisTrack general ledger account and VAT code. When the order reaches BisTrack, it uses that mapping to post revenue to the correct account. iWeb builds and tests this mapping so that your monthly P&L rolls up cleanly from transactional orders.

Yes. iWeb configures commerce to route orders to BisTrack with channel-specific fields so that B2B orders (e.g., with purchase order numbers and net terms) and B2C orders (e.g., with payment captured) are both acknowledged and fulfilled correctly. Pricing and credit rules can differ by channel if you set them up in BisTrack.

Refunds are initiated in commerce or your OMS and flow to BisTrack as credit memos. BisTrack generates a credit note and posts it to the customer account. The credit note flows back to commerce for customer visibility. iWeb ensures that refund amounts reconcile to the original invoice so that finance has a clear audit trail.

Physical counts and variances are recorded in BisTrack as stock adjustments. These adjustments flow into the next stock refresh cycle and update commerce. iWeb monitors the variance between published stock and actual allocations so that large discrepancies are flagged for investigation.

We recommend managing all pricing in BisTrack to keep it single-source. If you need short-term overrides (e.g., flash sales), you can implement them in BisTrack and republish, or manage them in a separate promotion engine that sits ahead of BisTrack pricing. Overriding BisTrack prices in commerce creates reconciliation risk and should be avoided.

iWeb builds dashboards and alerts for failed order submissions, stock sync delays, pricing drift, and credit lookup failures. You receive daily reports of exception queues and can drill into individual transactions. Critical failures (e.g., stock not updated for 2 hours) trigger immediate alerts to your operations team.

BisTrack tracks inventory by warehouse and location. When an order arrives, BisTrack's allocation engine assigns items to the nearest fulfillment centre or follows a routing rule you define. iWeb ensures that orders are marked with their assigned location so that logistics can pick and pack correctly.

The integration is built on BisTrack's standard APIs and data structures, so upgrades typically require only testing. If you migrate to a different ERP, iWeb can rebuild the integrations to the new system. We document all field mappings and logic so that the data model is portable.