Omnichannel Wholesale Explore

Overview: The Omnichannel Wholesale explore provides a combined view of weekly performance in the wholesale channels, merging internal shipment data and distributor portal sales data【26†Description】. It is designed to give a complete picture of revenue and volume trends for the wholesale portion of the business. This means it accounts for sales that happen via wholesale partners, including both the sell-in (what you ship to wholesale accounts) and sell-through if available (what distributors or B2B customers have sold onward, if reported). It’s particularly useful for operations teams overseeing wholesale channels, especially when multiple data sources are involved (like ERP shipments and external sales reports).

Included Data in Omnichannel Wholesale

• Internal ERP Shipment Data: This is the “sell-in” data – units and revenue of products shipped from your company to wholesale customers (e.g., shipments to a distributor or retail partner). These often come from an internal system (ERP or order management).

• Distributor/Retailer Sales Data: Some wholesale partners provide point-of-sale or depletion data (for example, if you work with a distributor that provides how much they sold to stores or how much was sold through to consumers). The explore integrates those to present a fuller picture.

• Weekly Aggregation: The data is on a weekly basis (consistent with other unified explores). Key metrics are:

  • Wholesale Revenue (likely the shipped revenue for the week, possibly also distributor sell-through revenue if captured).

  • Units Shipped and/or Units Sold (depending on which aspect is measured – possibly both, but usually focus on shipped units since that’s what you book as wholesale revenue).

• Channel Breakdown: Possibly, dimensions might include wholesale channel or partner name:

  • e.g., Distributor A, Distributor B, or types like Domestic Wholesale vs International, etc., to slice performance by partner.

• Complete Picture: Because not all wholesale accounts report sales, the description indicates it combines what’s available to form completeness【26†Description】. If a certain distributor doesn’t give sell-through, you at least have your shipments to them to gauge performance.

Use Cases for Omnichannel Wholesale

• Wholesale Performance Monitoring: See how the wholesale segment is doing overall:

  • Are wholesale revenues trending up or down weekly?

  • How do volumes compare to prior periods?

• Channel Management: Compare performance across wholesale channels (if you have multiple distributors or retail partners):

  • Perhaps one partner is driving growth while another is lagging.

  • Identify if any channel is underperforming relative to shipments (e.g., if sell-through is far below sell-in, maybe inventory is piling up at the partner).

• Operational Planning: Wholesale often involves bigger shipments but less frequent. This explore can highlight surges (maybe a big pipeline fill order at quarter start) or lulls (no reorders from a partner in several weeks).

• Target Setting: If you have targets for wholesale channels, you can use this to track actuals vs plan (especially if combined with a forecast or plan dataset).

Data Integration Details

• Sources:

  • ERP/Order Data: Likely provides fields like order date, quantity, and value for wholesale orders shipped.

  • Distributor Portals: e.g., If you use a system like EDI or portal that gives weekly sales to retail from the distributor, those are integrated.

  • The Sources field in CSV was NaN for this, but context says “distributor portal sales data”, indicating external sources like maybe Syndicated wholesale data or partner reports (perhaps SPINS or Nielsen might not cover B2B, so likely direct distributor feeds).

• Unified Metrics: It probably aligns metrics like “Net Sales (Wholesale)” – possibly at cost or wholesale price – and units. Volume trends can include both shipments and consumption if both available.