You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we have multi-location businesses, we use POS profiles to manage the billing configuration like price list, warehouse, cost centre, and accounting settings.
We no longer handle the online website as an added location in our multi-location environment. We need to support the Omni channel experience for our customers from each location and provide a more specific connection to the nearest outlet.
But the existing "WooCommerce Settings" on the ERPNext help us in the following scenarios only,
Single location Business (Online & Offline)
Online as an Additional Location
With the existing setup, we can't have a real Omni channel experience like each location has its own web space to deal with stock, price and offers specific to the area or outlet. like,
In WooCommerce (Part 1 - Available Already):
The multi-location businesses can make use of Multi-Site WordPress Configurations along with WooCommerce to handle this location-specific personalization like stock availability, location-specific price and connect the outlet team directly for quick response to the order fulfilment.
In ERPNext (Part 2 - Solution): Like POS Profile in ERPNext, we can have multi-record configurations for Woocommerce Settings as well. so that, we can connect to either a single website or location-based multiple endpoints (different URLs). This will enable the location to update the live stocks & latest prices quicker to the respective website endpoint and get the customer's details to the outlet directly.
So the consumer will get the real Omni channel experience on this setup and the businesses can automate lots of manual processes and workarounds.
Additional context
Automatic Item Master Updation to the Respective URL or endpoints (Single ERPNext Items -> Every Location Woocommerce Items)
Automatic Mapping of Cost-Center, Warehouse for Sales Orders at ERPNext
Automatic Price Updation to the Respective URL or endpoints
Automatic Stock Updation to the Respective URL or endpoints
Seamless Experience between Online & Offline (Auto Sync Frequently)
The text was updated successfully, but these errors were encountered:
Problem Description
When we have multi-location businesses, we use POS profiles to manage the billing configuration like price list, warehouse, cost centre, and accounting settings.
We no longer handle the online website as an added location in our multi-location environment. We need to support the Omni channel experience for our customers from each location and provide a more specific connection to the nearest outlet.
But the existing "WooCommerce Settings" on the ERPNext help us in the following scenarios only,
With the existing setup, we can't have a real Omni channel experience like each location has its own web space to deal with stock, price and offers specific to the area or outlet. like,
Physical Location_1 = brand.com/location_1
Physical Location_2 = brand.com/location_2
Physical Location_3 = brand.com/location_3
Solution
In WooCommerce (Part 1 - Available Already):
The multi-location businesses can make use of Multi-Site WordPress Configurations along with WooCommerce to handle this location-specific personalization like stock availability, location-specific price and connect the outlet team directly for quick response to the order fulfilment.
In ERPNext (Part 2 - Solution):
Like POS Profile in ERPNext, we can have multi-record configurations for Woocommerce Settings as well. so that, we can connect to either a single website or location-based multiple endpoints (different URLs). This will enable the location to update the live stocks & latest prices quicker to the respective website endpoint and get the customer's details to the outlet directly.
So the consumer will get the real Omni channel experience on this setup and the businesses can automate lots of manual processes and workarounds.
Additional context
The text was updated successfully, but these errors were encountered: