Skip to main content

Aggregated Replenishment

When handling Replenishment, it is possible to select an 'aggregated Store'.

image.png

This will aggregate figures for the Store, along with any other Store that uses it as a default receiving Store (See Stores for more information on this). 

The way this works is as follows:

  • Store A is set up to automatically receive its won POs
  • Store B is set up with Store A as its 'default receiving store'
  • Store C is set up with Store A as its 'default receiving store'

image.png

Stores A, B and C can be shown independently, or Store A can be shown in 'aggregated' view. If so, the Replenishment screen will retain the same layout, but the data will change.

Field Summary

It is possible to filter to an 'aggregated view' - for more information, click here.

Field Purpose

Dated figures (e.g. preceding and succeeding months, as well as last 12 months and month to date)

 

 

This data is aggregated

 

These columns include the sum of all stock despatched from the selected Store and dependant Stores, as well as all stock in locations in that Store and its dependant Stores, which is currently reserved to Sales orders, no matter the selling Store. 

 

That means:

 

  1. Stock already despatched from the selected Store and dependant Stores
    • Anything physically sent out from that Store is included.
  2. Stock reserved in that Store for Sales orders
    • Any stock sitting in locations within that Store, but already allocated to a Sales order, is also included.
    • This still counts even if the order was placed against a different selling Store.
Available Stock

This data is not aggregated

 

This shows the amount of stock currently available within the selected Store only
Available for Replenishment

This data is not aggregated

 

This shows the amount of stock currently available for replenishment within the selected Store only

 

To be eligible for replenishment, that stock must be available, and the Store must be marked as enabled for replenishment
Stock Pending Transit

This data is not aggregated

 

This shows stock currently in thetransit to this Store only,or one of its dependant Stores

 

This will include all units of stock be on a Stock Transfer which is 'in transit', and any outstanding units of stock on an open Stock Transfer which is 'Received (In Progress).
Stock on Order

This data is not aggregated

 

This shows stock currently on a Purchase Order, which is being delivered to the selected Store only
Required for Orders

This data is aggregated

 

This shows stock required for sales orders where the selling Store is the currently selected Store or one of its dependant Stores
Low Stock (order at)

This data is not aggregated

 

This shows the Low Stock figure

 

This is set against the Variant
High Stock (order to)

This data is not aggregated

 

This shows the High Stock figure

 

This is set against the Variant
Last Order

This data is not aggregated

 

This shows the date of the most recent Purchase Order for each Variant, received at the current Store
Suggested qty to order

This data is aggregated - this will take into account stock used in all linked Stores

 

This shows a recommended quantity to order, based on the data in this report; this may either be in the form of:

 

  • A Purchase Order
  • A Stock Transfer (if there is suitable stock available for replenishment)

How does it work?

Aggregated Data

  • Sales Data will be aggregated for sales across Stores A, B and C
  • Stock Data will be aggregated across Stores A, B and C - this includes:
    • Available Stock
    • Available for Replenishment
    • Stock Pending Transit
    • Stock On Order

Data That is Not Aggregated

Some data is not aggregated:

  • Required for Orders (this is Store specific, and is managed via the Required Orders screen)
  • High/Low stock figures (these are Store specific, and in aggregated view, default to just the selected Store only)
Back to top