How suppliers can share data with their resellers

Weavo connects multibrand resellers with their suppliers and automatically imports master data and shipments into the resellers pos and ecom.

Free!

Its 100% free to share data with your resellers using our platform.
The resellers pay weavo a monthly fee for the automation we do for them.

The only thing you need to do is provide us with a way to get hold of master data, order confirmations and shipment information digitally.

Why

Retailers spend countless hours manually entering product details—like GTIN-codes, images, descriptions, colors, prices and so forth — into their systems every time they receive goods.

They need to update order information, shipment quantities, and unit prices for each shipment coming from suppliers.

Automating this process frees up time, reduces errors, and gets products in store and online faster.

With accurate data flowing automatically, retailers can even rank higher on Google Shopping and stay ahead of the competition.

What's in it for me (as a supplier)

First of all, way more efficient resellers as all your shipments will be automatically available in the resellers pos. (have a look at this video how it works)
By ensuring your resellers have accurate GTINs in their POS and eCommerce systems, you gain access to real-time stock levels and sales performance directly from their stores.

If your system can receive stock and sales data, you can automate replenishment suggestions or even enable auto-replenishment, reducing “sold out” situations and increasing sales for both you and your resellers.

If you don’t have an integrated system, you can still benefit from automated Excel reports containing the same insights, allowing you to make data-driven replenishment recommendations to your resellers.

What data to share

Here's the list of what data you as a supplier should share with your reseller.

Your attribute names doesn't have to be the same as below.

Master data / PRICAT

Master data means all product data about each variant.

Please see the below list of product attribute requirements. The more data you as a supplier can share, the better for the resellers.

StyleNo (Mandatory)
The unique identifier assigned by the brand for this specific style.
Example: "315122"
StyleName (Mandatory)
The name of the product as recognized by the brand.
Example: "Nike Air Max 90"
Style Color Name (Mandatory)
The official color description for the product.
Example: "Ocean blue"
Color Name (Optional)
The main color for the product.
Example: "Blue"
Color Code / Variant (Mandatory)
The unique code that refers to the colorway of the product.
Example: "111"
Collection/Season (Mandatory)
The seasonal collection the product belongs to.
Example: "Spring/Summer 2024"
Product Type / Product Group (Mandatory)
The category or product group for classification.
Example: "Sneakers"
GTIN/EAN (Mandatory)
The global identifier used for tracking products.
Example: "0019123456789"
Size (Mandatory)
The size information for the product.
Example: "Small, Medium, Large"
RrpPrice (all available) (Mandatory)
The recommended retail price for all available currencies.
Typically this is one column per currency.
Example: "1499"
Composition (Optional)
The materials used in the product's construction.
Example: "80% cotton, 20% lycra"
SKU (Optional)
The internal stock-keeping unit number for inventory management.
Example: "SKU123456"
CustomsCode (Optional)
The code used for international shipping and customs by resellers who sell online abroad.
Example: "6403 99 90"
Country of Origin (Optional)
Where the product was manufactured.
Example: "Vietnam"
Brand Name (Mandatory)
The brand associated with the product.
Example: "Nike"
Description of Product for Online Stores (Optional but highly recommended )
A brief product description to be used for e-commerce listings.
Example: "The Nike Air Max 90 stays true to its roots with an iconic Waffle sole, stitched overlays, and classic TPU accents."
Product Images (Mandatory)
Images showcasing the product.
We prefer to get product image urls as part of the master data.
Else we can get images from you by FTP or via API from your DAM/PIM/ECOM solution. Dropbox or similar is also okay, but last resort.

Order Confirmation / ORDRSP

OrderNo (Mandatory)
Unique identifier for the order.
Example: "ORD12345"
OrderDate (Optional)
The date when the order was placed.
Example: "2024-03-15"
Qty (*) (Mandatory)
Quantity of the product ordered.
Example: "10"
Ean and/or Sku (Mandatory)
The EAN (GTIN) or SKU identifier, depending on the available master data.
Example: "0019123456789" or "SKU123456"
UnitPrice (Mandatory or in Shipment)
The price per unit for the ordered product.
Example: "€150"
Currency (Mandatory or in Shipment)
The currency code for the UnitPrice.
Example: "NOK"
CustomerId / GLN (ShipTo) (Mandatory)
The unique identifier or GLN (Global Location Number) for the customer receiving the order.
Example: "CUST789" or "GLN1234567890123"

Shipment / Packing Slip / DesAdv

ShipmentNo (Mandatory)
Unique identifier for the shipment, assigned by the supplier.
Example: "SHIP12345"
OrderNo (Mandatory)
The corresponding order number from the order confirmation.
Example: "ORD12345"
ShipmentDate (Mandatory)
The date when the shipment was dispatched.
Example: "2024-03-16"
ExpectedDeliveryDate (Optional)
The date when the shipment is expected to arrive.
Example: "2024-03-18"
Quantity (Mandatory)
Quantity of the product being shipped.
Example: "10"
Ean or Sku (Mandatory)
The EAN (GTIN) or SKU identifier for the product in the shipment.
Example: "0019123456789" or "SKU123456"
UnitPrice (Mandatory either on shipment or Order Confirmation)
The price per unit for the product in the shipment.
Example: "150"
Currency (Mandatory or in Shipment)
The currency code for the UnitPrice.
Example: "NOK"
CustomerId / GLN (ShipTo) (Mandatory)
A unique identifier or GLN for the customer receiving the shipment.
Example: "CUST789" or "GLN1234567890123"

How to share data

There are many ways for suppliers to share data with their resellers.

Weavo support almost any transfer method and format.

FTP

We can either connect to your FTP or you can send files to Weavo´s sFTP.
Whatever you prefer as a supplier.

API

If you have an API from your B2B-portal, ERP-system, PIM or DAM, we can connect to it and retrieve data. All you have to do is make sure we get access.

Our Ready-to-use integrations

Mail

Some systems can automatically send emails with orders and shipments with attachment included.
If you prefer to setup automatic emails, you can send them to our email address.

File formats

Weavo support just about any format our there.

EDIFACT (PRICAT, ORDRSP, DESADV)
Json (from any api)
Excel
XML
CSV
Text