Skip to main content
All CollectionsTraining/Application
Self-study: Preparation for purchasing / ordering (with analytics)
Self-study: Preparation for purchasing / ordering (with analytics)
Desiree Alge avatar
Written by Desiree Alge
Updated over a week ago

0.0 Important preliminary information

0.1 First, some information on the processing of data

The "2a_Dashboard (Eingänge vs. Verkäufe)" dashboard retrieves the data from the movements or movement date.

The "Datum von-bis" filter retrieves all movement data from the selected date range (movement date):

  • Receipts, store transfers and returns (shipments)

  • Sales (transaction)

In Analytics, statements can only be made to the extent that they have been entered in full. Above all, the tag "Saison" was set for each model. (We have created a control dashboard for this (see 1.)

Without entering the tag filter, e.g. "F/S 23", sold items from other seasons are also calculated in the selected movement date range.

0.2 Important information on EDI supplier data

At the moment, we have no influence on what "saison tag" data is sent in by EDI suppliers.

In some cases, no order (ORDRSP) is sent for subsequent deliveries from EDI suppliers, only the delivery note (DESADV).

--> This is why analyses of the order type from EDI suppliers are not useful!

(Question 4 + 5 by order type)

In the "von-bis" date filter, the incoming and sales dates are grouped together.

The "Datum von-bis" filter must be adjusted.

If the tag filter is not entered, sold items from other seasons are also calculated in the selected date range.

If the tag filter is entered, only receipts and sales of models with this day are analysed.

Explanation of the column titles

  • Shipment_Quantity = Quantity received

  • Transaction_Quantity = Quantity sold

  • Shipment_EP_Wert_CHF = Incoming value in CHF

  • Transaction_EP_Wert_CHF = Sales value at cost price

Preliminary information: we have already started to programme two new fields in the model.

Field 1 "Saison": This allows the uncontrolled growth of EDI suppliers' season tags to be converted to a separate system. The aim is for our system to attempt to pre-place the most suitable season code with EDI suppliers.

Field 2 "Collection": In this field, further customised refinements can be specified individually by supplier. E.g. delivery month, pre/main collection etc., which will enable even more detailed analyses in the future.

1. Preparation for purchase for all customers who have already been live for a full season:

1.1 Control "tags" in models with the season code

in Analytics "Movements"

Das Datum fragt auf das Eingangs-Datum (Shipment) ab.

Check the "Tags" column to see whether the appropriate season is listed.

Add any missing "tags" in the admin app/article tab: "edit".

There can also be several seasons for basic articles

1.2 Analyses with "tags" of a season

in Analytics "Movements"

1st question: sorted by supplier

2nd question: sorted by supplier/model

3rd question: sorted by supplier/model/colour

4th question: sorted by size

1st question: sorted by store/supplier

2nd question: sorted by store/supplier/model

3rd question: sorted by store/supplier/model/colour

4th question: sorted from store to size

for EDI suppliers with delivery months

Analyses for order types

Important: Questions 5 + 6 may be too low for analyses for "EDI suppliers" because EDI suppliers sometimes do not send an order (ORDRSP) for subsequent deliveries.

5th question: sorted by order type (order type)

6th question: sorted by supplier/order type

1.3 More helpful analytics dashboards for purchasing

Analytics/Management

helpful for overview sales and entrances/sales/warehouse with branch subdivision

The quantities sold of a size can be queried here

2. Preparation for purchase for all customers who are not yet live for a full season:

Because there is not all the transaction data (incoming goods, returns, etc.) for the entire period, the incoming data and therefore the sales data are not correct.

This means that a different derivation of figures must be made for purchasing.

1. budget basis with sales period in pcs. and CHF

--> This is the required purchase quantity and forms the basis for the budget calculation

With the sales report Umsatzreport 5_Verkauf, click on Title to come into the detailed question. Then click on "Cloud" at the bottom right and download as Excel.

2.Assessment of sell-out in CHF and pcs.

Should the purchase quantity be corrected due to sell-out?

See the markdowns in the sales report

-->The correction would change the purchase quantity!

3. assessment of current stock in CHF and units.

Should the stock be higher or lower at the end of the next sales period?

With stock/supplier (today)

Here it is worth taking a physical look at the departments and briefly checking the effective stock levels and the list

-->The correction would change the purchase quantity!

4. calculation of total budget (100%)

Prepare with Excel

+Sale of the period

+/- correction sell-out

+/-correction final stock

= Purchase budget for subsequent period 100%

5. budget distribution to suppliers with order dates

Pre- and main order in %

Post/release order in %

Please note: EDI suppliers with Auto-QR/Refill receive lower pre-order budgets or larger reassessment budgets.

Did this answer your question?