05-11-2023 08:50 PM
First off, we use simply packaging hierarchies - usually case to each with the case as the highest level of the hierarchy, so I am unfamiliar with data required for a pallet hierarchy and from pallet to case to child. Is it possible to establish a pallet level to these existing case / each hierarchies? I am assuming the steps would be to register the new pallet GTIN's & then linking the case to the pallet which should pull the child link with it, correct? We have many case GTIN's where the each / child GTIN is the same (case pack of 6, case pack of 12). The pallet GTIN's would be unique in the same way - one pallet GTIN for the case pack of 6 to child and another pallet GTIN for the case pack of 12 to child. The one thing I am not really sure about is the non-GTIN pallet level ti & hi / total case info we have on the current case levels. If we establish a pallet GTIN, then we need to change the info from the non-GTIN pallet ti & hi to the GTIN pallet ti & hi, correct? And is this same info recorded under the pallet GTIN?
Additionally, we would like to update each level of the hierarchy as being orderable. The each would remain the base unit and the consumer unit. If all levels of the hierarchy is orderable, can they / should they also be a dispatch unit & invoice unit even the base / consumer unit?
05-12-2023 12:01 PM
Yes, @kxsRSC changing an indicator from False to True will be just an update. If you change from True to False, be careful, per the article I shared, you will need to have at least one True for every one across the hierarchy
05-12-2023 09:06 AM
Hello @kxsRSC and welcome back. Thanks for all the details in your question as it helps me make sure you are getting the support you need. For my response, I am assuming you are asking as you have a trading partner asking you to add pallet-level GTINs to existing hierarchies. If I am wrong about that please let me know.
You have your finger on the pulse of most changes you would need to make for your items to add a new hierarchy with a Pallet/Case/Each in addition to your Case/Each structure. One of the biggest challenges will be due to the standardized rule that you cannot change the hierarchy structure for items published to trading partners. This means, for any hierarchies that are currently Case/Each that you want to add a pallet above the Case, you will have to withdraw the publications, wait 25 hours, then make the changes you need.
05-12-2023 10:20 AM
Hi - yes, you have clarified what I would need to do to introduce the pallet level GTIN - thank you.
Can you please confirm that I can have each level with the hierarchy as orderable - true? And, can we also make each level a dispatch unit - true & invoice unit - true?
One other additional question - Would we be able to use the our same sku # for the Manufacturer's identifier for both the pallet GTIN and the case GTIN (since we may maintain this information in an alternate UOM table under one sku # on our end)?
| Alternate Item Identification Agency | Alternate Item Identification ID |
| alternateItemIdentification/agency | alternateItemIdentification/id |
| 90 -- Assigned By Manufacturer | 10000521 |
05-12-2023 11:02 AM
Hello @kxsRSC and thanks for getting back to me. For the Unit Indicators, I just posted This Article earlier this week if you want to take a look. In addition to this article and specific to your questions, you should mark items as orderable if they are item levels from which your trading partners order from you. If they order by Pallet, Case and/or Each, you should flag that as true on the appropriate levels. This is also true for Invoice Indicators. Your dispatch unit should be True for the level you ship at. Your Base unit Indicator should only be on the Each or bottom level of your hierarchy.
Regarding your last question, I am not sure I fully understand. I you are asking if you can use the same GTIN for two levels of the hierarchy, the answer is No. Can you clarify that one fo rme?
05-12-2023 11:20 AM
Hi - I will take a look at the article you provided & let you know if I have any more questions on indicators. Regarding your question - the GTIN's for pallet and for case would be unique but we have some retailers that require us to supply the alternate item identification which we use our sku # assigned. When I supply the pallet GTN level of data (which will be a unique GTIN) and the case GTIN level of data (again a unique GTIN), can I use the same sku # in that alternate item identification field for both levels? We plan to house both unique GTIN's for pallet & for case under one sku # in our system on an alternate UoM table.
05-12-2023 11:37 AM
@kxsRSC Yes, you can use the same SKU for both. That is an internal identifier for you.
05-12-2023 11:48 AM
Thanks for making the sku situation clear. I have one more question regarding the indicators. If I switch any indicator on the each GTIN level from false to true (ordering, dispatch, invoice) will it record it as just an update or will I need to do anything additional?
05-12-2023 12:01 PM
Yes, @kxsRSC changing an indicator from False to True will be just an update. If you change from True to False, be careful, per the article I shared, you will need to have at least one True for every one across the hierarchy
05-12-2023 12:04 PM
As always - awesome help!!!! Thank you for your time!
05-12-2023 12:08 PM
Happy to do so, let us know if you need anything else...