Order Sync Settings | Product Prices, Currency & Order Sync Scope – OneWarehouse

Sync Order Settings (Product Pricing and Currency Rules)

Overview

After you bind a store on an e-commerce platform (such as Shopify, SHOPLINE 2.0, or TikTok) to OneWarehouse (OW), the system will automatically sync the store's order information. To meet merchants' diverse operational needs, OW's "Sync Order Settings" provides the following two core customization features:

Order fetch range (New feature ✨): You can accurately filter orders based on the upstream platform's "fulfillment locations" and fetch only orders that need to be processed by OW, preventing unrelated orders from causing interference.
Product pricing and currency rules: You can choose whether product prices in synced orders use the "platform checkout amount" or uniformly use the "OW system pricing" (commonly used for cross-border customs declarations).

Key Limitations and Important Notes (Very Important)

⛔️ OW product unit prices must not be 0
Regardless of which pricing mode above you select, you must ensure that the "product unit price" in the OW system is greater than 0 and is not blank.
Risk warning: If the product unit price is 0, an order may encounter an error or be unable to continue processing when it is exported for shipment or undergoes customs declaration because the system cannot identify a valid price.

⚠️ Scope of product pricing settings
Product pricing settings apply only to automatically synced orders from bound stores.
Orders created through "Manual Creation," "Bulk Excel Import," or "OpenAPI Integration" are not subject to this rule. The system will directly use the price entered when the order was created.

⚠️ Notes on the order sync range
At least one location must be retained: When customizing the fetch range, the system will require you to select at least one fulfillment location. If you deselect all locations, the system will be unable to save the settings because this is equivalent to stopping all order syncing for the store.
Effective time: After you modify the "order fetch range," the settings will take effect starting with new orders created after the next automatic sync. If you deselect a location, historical orders from that location that were previously synced to OW will not be automatically removed. You must manually void them in the OW system.
Linked to the location status on the platform: If you deactivate a fulfillment location on the upstream platform (such as the Shopify admin), the system will mark that abnormal location the next time you open the OW settings window. After you save the settings again, OW will automatically remove the invalid location from the fetch range.
Differences in platform support: Not all sales platforms support filtering orders by "fulfillment location." Currently, OW supports filtering orders with multiple fulfillment locations on Shopify, SHOPLINE 2.0, and TikTok only. If your store does not belong to one of the platforms above, the system will display "Not currently supported" and will, by default, fetch all orders.
At least one location must be retained: When customizing the fetch range, the system will require you to select at least one fulfillment location. If you deselect all locations, the system will be unable to save the settings because this is equivalent to stopping all order syncing for the store.

Core Feature 1: Set "Product Pricing and Currency Rules"

Based on your accounting and customs declaration needs, the system provides the following two pricing modes:

Mode A: Prioritize the product price in the order (System default)

How it works: The system will prioritize obtaining the actual product price and currency paid at checkout in the upstream platform order.
Fallback mechanism: If the product price sent by the platform is 0, blank, or another abnormal value, the system will automatically use the product unit price and currency maintained in the OW system to ensure that the order can proceed to subsequent processes.
Applicable scenarios: Suitable for sellers whose product prices frequently change due to platform promotions and who want to use the actual amount paid by the customer at checkout as the basis.

Mode B: Prioritize the price in OW product information

How it works: Regardless of the actual purchase amount paid by the customer on the platform, the system will always use the unit price and currency set in the OW product file as the order value.
Applicable scenarios: Suitable for cross-border sellers or B2B businesses where the customs declaration or outbound value must be calculated according to fixed standards and must not be affected by front-end promotional discounts.

Change the Store's Sync Pricing Mode

Go to [Settings] > [Sales Platform Settings], find the store you want to configure, click the "... (More Actions)" button on the right, and select [Sync Order Settings] from the drop-down menu.
Select the desired mode in the pop-up window:
- Prioritize the product price in the order
- Prioritize the price in OW product information

After making your selection, click "Confirm" to apply the settings.

Check and Maintain OW Product Prices (Abnormality Prevention Check)

To prevent errors caused by a product price of 0, regularly check product prices in the OW system:

Go to [Products] > [Product Management], search for a product by SKU or product name, and click [Edit Product] on the right of the product.

On the product details page, find and set the "product unit price" and "currency unit." Confirm that the product unit price is > 0 and that the currency unit is not blank, then save the settings.

Core Feature 2: Set the "Order Fetch Range (Fulfillment Locations)"

💡 Why set a fetch range? Many e-commerce platforms support multiple fulfillment locations, such as OW warehouses, third-party overseas warehouses, and physical stores. Without restrictions, OW will fetch all orders from the store, requiring operations staff to spend considerable time each day manually excluding orders that do not need to be shipped by OW.

A. Sync all locations by default

By default, the system selects all fulfillment locations.

If you do not modify the "order sync range," store orders that meet the order sync conditions will be synced normally to OneWarehouse.

B. Sync only specified fulfillment locations

If orders from certain fulfillment locations do not need to be processed by OneWarehouse, you can deselect the corresponding locations.

For example, your store has the following three fulfillment locations:

OW Warehouse
Store
3PL Warehouse

If only orders from OW Warehouse need to be fulfilled by OneWarehouse, you can select only:

☑ OW Warehouse
☐ Store
☐ 3PL Warehouse

After the settings are completed, new orders assigned to Store or 3PL Warehouse will no longer be synced to OneWarehouse.

⚠️ Modifying the sync range affects only new orders created after the settings take effect.
Orders already synced to OneWarehouse will not be affected and will not be automatically deleted or canceled because a fulfillment location was deselected.

C. Steps

Go to 〖Settings〗 > 〖Sales Platform Settings〗 and find the store you want to configure.

You can enter the settings in either of the following ways:

Click "... (More Actions)" > 〖Sync Order Settings〗 on the right;
Click "All Locations" or "x/y Selected" under "Order Sync Range" in the list.

In the "Sync Order Settings" window, find 〖Order Sync Range〗.

The system will display the fulfillment locations available for the current sales platform store, with all locations selected by default.

Select the fulfillment locations whose orders need to be synced to OneWarehouse, and deselect the locations whose orders do not need to be fulfilled by OneWarehouse.

After a fulfillment location is deselected, new orders subsequently created for that location will no longer be synced to OneWarehouse. Already synced orders will not be affected.

After completing the settings, click "Confirm."

The settings will take effect during the next automatic order sync.