Following a meeting 18th March 2022 ROOM the following was discovered with regards to the ROOM software design:

...

ROOM Process Flow

ROOM have the following entities in their system

...

Communication ROOM - SEKO

Suggestion 1

Allow

...

both API calls to the same end point which overlay data for the White Glove

...

booking

that the The payload for ROOM for sales orders and purchase orders goes to the same end point and has the same reference number (SEKO External Ref).

...

In this way the White Glove data would end up with SKUs and instructions on the same booking.

Suggestion 2

ROOM combine data into one API call

ROOM could choose to combine all the data into one API call which would exactly match the SEKO White Glove API.

SKU Layouts

ROOM SKU Layout V1 2020 - 2022

There was always a parent SKU with an apparently unordered set of child SKUs

...

ROOM sends the SKUs as parent and all children including with no direct link between parents and children

ROOM SKU Layout V2 2022 -

Kits (eg. complete meeting rooms)

...

ROOM rely on serial numbers for customer services to be able to identify the piece in question.

Dispatch note / API contains all SKUs which are picked and their serial numbers. There is no concept of parents and children.

QUESTION

Serial numbers are allocated on picking from a location (correct?). Are serial numbers allocated only when they leave the warehouse and not during the manufacturing process? Dispatch note / API contains all SKUs which are picked and their serial numbers. There is no concept of parents and childrenif they were to be tracked from the manufacturing process they would be able to be tracked all the way back there, not sure if that is possible now.

Suggestion

The sales order is sent to the warehouse; this includes a list of SKUs

...