Scayle and Orderwise
Integration Agency & Consultants
Intelligent Consulting
Detailed Solution Design
Smooth Integration
Visibility
Training
BigCommerce
Common failures
Inventory latency and overselling
Operational impact: When stock level updates from Orderwise are delayed, Scayle can display incorrect availability, leading to overselling during peak trading. This forces the customer experience team to manage cancelled orders and complaints. It also creates wasted effort for the fulfilment team who process sales orders for items that are out of stock.
Prevention / Action: The integration should prioritise near-real-time delta updates for stock levels, rather than relying on slow, full-catalogue syncs. A process should be designed to push an inventory change from Orderwise to Scayle immediately a change occurs. For fast-moving SKUs, operational alignment is needed on using Scayle's stock buffers, balancing overselling risk against potential lost sales.
Duplicate sales orders
Operational impact: If an order sync from Scayle fails, an automated retry without proper checks can create a duplicate Sales Order in Orderwise. This may cause the fulfilment team to pick and ship the same order twice, resulting in financial loss and complicating the returns process. The finance team must then spend time identifying and reconciling these duplicates in the ledger.
Prevention / Action: The integration must ensure order posting is idempotent by using a unique identifier from the Scayle order as a key. Before creating a Sales Order, the integration must check if a record with that unique ID already exists in Orderwise. A queueing system with clear status handling for each order ('pending', 'sent', 'acknowledged') helps manage retries without creating duplicates.
Mismatched order and fulfilment status
Operational impact: If Orderwise dispatches an order but the fulfilment confirmation fails to update Scayle, customers do not receive their 'order shipped' notification or tracking number. This typically increases 'Where Is My Order?' (WISMO) queries, placing avoidable load on the customer service team and damaging customer confidence.
Prevention / Action: Define the specific Orderwise event (e.g., status change to 'Despatched') that should trigger the fulfilment update to Scayle. The integration requires robust monitoring and exception handling. An alert should be raised if a fulfilment update is sent by Orderwise but not successfully acknowledged by Scayle within a defined timeframe, allowing operations to intervene.
Financial reconciliation gaps
Operational impact: Discrepancies between the final order total in Scayle and the corresponding sales order value in Orderwise create significant manual work for the finance team. These gaps often result from differences in how each system calculates tax, allocates discounts, or applies shipping fees. This forces line-by-line checks during the month-end close process, delaying financial reporting.
Prevention / Action: Establish which system is the source of truth for pricing calculations, which is typically Scayle at the point of transaction. The integration logic must explicitly map all financial fields, including item-level discounts and specific tax treatments, between Scayle and Orderwise. A scheduled exception report should be designed to automatically flag orders where the totals do not match, enabling proactive correction.
Frequently asked questions
How does this integration prevent us from overselling on Scayle?
The integration establishes Orderwise as the central source of truth for inventory. Stock levels are synced from Orderwise to Scayle on a defined schedule, ensuring your web-front accurately reflects available warehouse stock. This prevents the sale of out-of-stock SKUs, reducing the need for backorders or cancelled sales that damage customer trust.
How does the integration speed up our month-end close process?
The integration automates the posting of sales orders from Scayle directly into Orderwise, removing the need for manual data entry by the finance team. This ensures revenue data is consistent across both systems from the point of sale. As a result, the team avoids spending hours manually reconciling two different sets of order data, which is a common cause of month-end delays.
What happens if a Scayle SKU doesn't match the item record in Orderwise?
Mismatched SKUs will cause the integration to fail when creating the sales order in Orderwise. The order from Scayle will be flagged and will not enter your fulfilment workflow automatically. This requires someone to manually investigate and correct the item record in either Scayle or Orderwise, causing operational delays.
Once an order is created in Scayle, where is it fulfilled from?
Scayle's role is to capture the initial sales order, which is immediately pushed into Orderwise. Once the order exists in Orderwise, it becomes the system of record responsible for the entire order-to-cash and fulfilment process. Any updates, such as an item fulfilment or despatch status, originate in Orderwise and are then synced back to Scayle to inform the customer.
If an order is cancelled in Scayle, does it automatically cancel in Orderwise?
Yes, in a correctly configured integration, cancelling an order in Scayle sends a signal to cancel the corresponding sales order in Orderwise. However, if the order has already been processed to a certain stage in Orderwise, such as 'picking in progress', it may not be possible to stop the shipment. This scenario would then require the item to be processed as a customer return.