UpShop FreshIQ POS Integration Specialists

iWeb designs stock allocation so ecommerce checkout holds inventory only from pools earmarked for ecommerce, and branch stock is reserved separately. Real-time stock updates from FreshIQ flow back to ecommerce so available-to-promise is accurate. Exception handling flags oversells so they surface before orders are committed.

Yes. iWeb establishes a pricing hierarchy where base pricing lives in ERP, branches can apply local rules within approval bounds, and ecommerce displays base pricing unless a customer buys in-store. Price change workflows define who approves, who publishes, and how exceptions are caught.

Not by default. iWeb builds daily reconciliation batches that post till transactions to ERP, match them against payments and customer accounts, and flag exceptions for manual review. Reconciliation timing and escalation rules are designed before launch.

iWeb configures the OMS or fulfilment system to recognize click-and-collect orders, route them to the requested branch, trigger a notification in FreshIQ or the branch till, and expect branch confirmation before the customer is notified as ready. Status flows back to ecommerce so customers see accurate collection timings.

iWeb links retail and trade accounts so a single customer can be recognized across channels. Account-level credit, pricing and history are unified. This requires account matching rules and periodic duplicate detection so the same person is never held twice.

Allocation rules live in the OMS or fulfillment service. iWeb defines the rules (distance, stock, capacity, delivery promise) and sets up monitoring so rule changes are tested before they go live and failures are visible.

iWeb designs the till-to-ERP link so FreshIQ can store transactions locally during an outage and replay them to ERP when connectivity returns. Reconciliation is idempotent so replayed transactions do not duplicate entries. Monitoring alerts staff if posting falls behind.

iWeb implements account matching logic that keys on email, phone or loyalty ID, and runs periodic duplicate detection. Matched accounts are linked so staff and ecommerce see the same customer record. Manual review handles true duplicates.

iWeb can support separate promotions if the system architecture allows (promotions engine separate from pricing). Typically, a single promotion is preferred to avoid customer confusion. If separate promotions are needed, governance rules and monitoring must ensure they do not overlap or conflict unexpectedly.

iWeb links the original online order to the branch system so a customer can walk in with a receipt and initiate a return. The return is recorded in FreshIQ and flows back to ecommerce and ERP so the refund, restocking and inventory adjustment are coordinated.

iWeb builds dashboards and alerts so you see till posting failures, stock sync delays, order routing failures and account-linking mismatches in real time. Daily monitoring reports and escalation queues ensure nothing silently breaks during peak trading.

iWeb typically designs near-real-time syncs (minutes to a few seconds) for stock adjustments so ecommerce availability is always current. Frequency and tolerance are set before launch based on trading patterns and system load.

iWeb queues the order until the branch comes back online, then delivers it with an alert. If the branch stays offline too long, escalation rules trigger (e.g., cancel the order, reroute to another branch, or notify the customer). Timeouts and fallback behaviour are configured per branch.