Retailer A only provides their internal product code in the ePOS sales file they share.
Retailer B shares store level ePOS sales, but does not share store numbers, only store names.
Use them both in Wieve. You really can Bring Your Own Data to Wieve in the format you receive it.
The products Retailer A is selling are sold by other retailers. To be useful sales need to be compared across both retailers. Wieve now maintains custom product mapping – per retailer – to bridge the gap from retail product code to barcode (EAN). This leaves you with full control in Wieve. Even if they share mapping and get it wrong you retain ultimate control and flexibility.
In the Greater London area Retailer B refers to a store as New Malden. Internally both at HQ and in the field your team knows the store only as Raynes Park. Yet without a store number in the sales file how do you assign sales to the correct store and label the store for your use? Wieve now maintains a custom store mapping – per retailer – to bridge the gap from shared store name, in the ePOS sales upload file, to a store in Wieve.
So call it whatever you like. Then change the name. Then change it back again. The sales will find the store however you refer to it.
And, of course, Wieve still automatically adds new stores detected in the ePOS sales upload file providing you instant notification and sales visibility. Much more useful than sales records which error out during processing.