Customers with multiple locations using talech can sync their inventory across locations. Highlights include:
- Sync support for products, categories, discounts, modifiers and suppliers
- Select specific attributes to sync
- Sync from any location and control which location to sync to
- Edit inventory levels for multiple locations through a single interface
- Note: Tags and bundle product sync should be available by the end of February
Single product sync
Note: talech uses the Item # field as the common identifier to match products across locations. Product sync will only work correctly if you have an item # specified or you do not change the item #.
If the product doesn't exist at the location being sync'd to, talech will create a new one (e.g. If you are editing a product at location A and it doesn't exist at location B, after the sync process, talech will update the product at location A and create a new product at location B.
Step 1: Select the location.
Step 2: Select the product you want to edit and select the sync button once done with your changes.
Step 3: Confirm the attributes that you want to sync. talech will pre-select the attributes that have changed.
Step 4: Select the location you want to sync to. Make sure the current location is also selected if you want to save your product changes to the selected store.
Step 5: Confirm your changes and sync.
Inventory update
You can edit the inventory levels for a product for multiple locations through a single interface.
Step 1: Select the product and select the "Inventory by Location" tab.
Step 2: Select the Edit button.
Step 3: Edit the inventory levels and save your changes.
Sync discounts, categories, modifiers and suppliers
For all other inventory objects, talech uses the name as the common identifier and supports a batch sync to update changes across locations.
Step 1: Select the Sync button.
Select 2: Select the discounts (or other inventory object) you want to sync.
Step 3: Select the locations you want to sync to.
Step 4: Confirm the sync.
Comments
0 comments
Article is closed for comments.