How does the interaction between BTC-Net and RetailVista work and how is support arranged?

This document describes the relationship between BTC and RetailVista. In fact, the overall environment is even more extensive: There is a BTC organization that uses RetailVista. This organization was created through a collaboration between Bosrand, Coppelmans, and Tuinwereld.

In the BTC RetailVista environment, products are created and maintained. These products are sent to the three separate RetailVista environments of Bosrand, Coppelmans, and Tuinwereld via a PriCat (product) message to RetailLink. To ensure that the barcodes do not conflict, 'own' barcodes are generated in the BTC environment from a unique range reserved by GS1. The use of 99 or 21 barcodes would cause major problems because the individual organizations also use that range.

The PriCat messages are automatically retrieved from RetailLink and read in with received EDI messages by RetailVista. It may be that a message contains new classifications, which requires a mapping between the classification in the EDI message and the classifications present in RetailVista. If one or more mappings are missing from a file, the message is rejected. All missing mappings are automatically created in 'Pricat translations'. The only thing that needs to be done there is to link all mappings that are not yet linked. Once all mappings are linked, all messages will be processed again in the next processing.

A peculiarity of the RetailVista BTC environment is that a BTC-Net website is linked to RetailVista. This is used to automate container administration. This concerns goods that are purchased from abroad.

In RetailVista on company 4, the container administration can be found. There, a 'sign-up' purchase order can be created, which essentially states what the organization plans to purchase. Sales orders can be linked to this sign-up order in RetailVista. These sales orders directly contain all the lines of the purchase order and only provide the option to specify quantities. No lines can be added, removed, or changed. As soon as a line is added or removed on the purchase order itself, it is immediately reflected in all linked sales orders.

Once all stores have signed up, the total desired quantities are known for the sign-up purchase order, and the sign-up order lines can be increased or decreased. Eventually, the sign-up order can be finalized and sent.

BTC does not yet utilize the possible return route when receiving products.

Support provision

NedFox does not provide support and has no knowledge of BTC Net. The agreement with BTC is that they submit any questions to the party the question is about. For example, if there is a question about a purchase order that is not visible in BTC Net, that question will be directed to Bratpack. If Bratpack needs our support to answer this question, they will ask NedFox, and NedFox will communicate it to Bratpack. Ultimately, Bratpack informs its customer.