The time has come, on 7 January 2019 the CCRFID (red labels) have to make room for the newCCTAG5labels from Container Centralen. Well begun is half done! But, what changes for the Avalanche/TrackOnline user?
Another name for the item is not sufficient
Why changing the name isn’t an option? Your clients, companies involved with returnable packaging, have the right to return the old CCRFID. After all, they’ve also received them before. On the other hand, you don’t want to return CCTAG5 to parties that previously delivered that amount to CCRFID. You too have the right to return it as CCRFID.
Should the item be named immediately with the amount still on the locations, then with a fluctuating amount it’s not possible to keep track of how many old red locks can be handed in and how much CCTAG5 should be handed in.
Do you use financial modules? Then it’s wise to maintain the current item. To keep control over the numbers with old label ‘in the field’, you can follow the next steps to keep Avalanche in order.
Actions assuming that the current CC is called CCRFID:
- Create a new item called ‘CCRFID old’
- Create a location under the Company called ‘RELABEL‘
- Subsequently, all final balances that are on locations on January 6, 2019 with item CCRFID, must be transferred to CCRFID old. The transactions can be created manually, whereby the balances to CCRFID are booked to location RELABEL and then the equal number of RELABEL is returned to item CCRFID old.
- After rebooking everything, you request a report from all customer locations on 6 January 2019. This report may not show any numbers on CCRFID.
- If at point four indeed all balances are zero for CCRFID, then CCRFID can be named after CCTAG5 in order to continue under that name from now on.
- After the above actions, it’s very important to regularly check whether the balances on 6 January 2019 for CCTAG5 remain zero. If this is not the case, then a booking has been made after 6 January 2019 with a transaction date before 7 January 2019. As soon as this happens you must look up the relevant location and adjust the numbers on CCTAG5 to zero and add the same number to CCRFID old.
External numbering from Royal FloraHolland on this item would remain the same, so that doesn’t require further action on the existing item.
No financial modules
If no financial modules are used. This is the simpler variant. There is no need to rebook here. It is sufficient to create a new item called CCTAG5 and all bookings with CC carts that go out or arrive after January 6, 2019 are booked on this item.
Anything that comes back on the old red label will also be booked on the old CCRFID. Customers have the right to return that number that was actually delivered to CCRFID in the past. Anything that is surrendered, you do not have to return as CCTAG5, but can also be sent back as CCRFID.
According to Royal FloraHolland, the item would remain the same, as well as the number for the item that is used. In this case, you have to decipher the old item CCRFID and link this number to CCTAG5. Don’t do this until January 7, 2019 when the previous period has been fully imported. So all transactions for January 7, 2019 at Royal FloraHolland must have been imported before making the adjustments in numbering.
If your customer has CCRFID numbers that you provide locks for, then these must be entered in your administration as received CCRFID and CCTAG5 delivered.
In this way, outstanding carts are drawn into the CCTAG5 balance without a physical shift taking place at your location. So only when the loose CCTAG5 locks are issued does this operation take place. This also applies in reverse if you receive loose locks.
Any doubt or questions?
If you have any doubts or questions, you can contact our support colleagues. They are happy to help you.