Getting Started
The wiki sections within this project will provide technical usage guidance for connecting, authenticating and transacting on the platform.
Contents
| Administrative | Technical |
|---|---|
| - Roles and responsibilities | - Installation process of supporting technologies |
| - Pre-requisites | - JSON Web Token usage - How do I get one and how do I use it |
| - Trading Partners | - Message structures and data attributes - message formats |
| - Legal Requirements | - Usage rules and business processes - what are required attributes, what do they mean and when do I use them |
| - GS1 membership and administration | - Samples: code and messages |
| - Internal processes | - Point in Process Integration |
| - Master data alignment | - Process flows() |
| - Attestation |
Obtaining credentials
This platform operates as a transactional processor with binding commitment on the messages posted or received hereon and as such, does require legally binding agreements to be in place between the trading entities.
In order to obtain credentials to the platform, legal agreement is required with at least one trading partner on the platform, or mandate from a value added networking partner:
Preparation
This document outlines administrative and process orientated pre-requisites to achieve maximum benefit from the operation on the STF platform and realise optimal performance with trading partners.
This is only a guide and detailed work programmes will be required to ensure that all requirements are met for your firm and trading partner requirements.
The Legal components discussed within this document must be read in conjunction with your national and local laws, regulatory rules, company polices and customer trading terms.
Roles and responsibilities
| Function | Commercial | Operations | Technology | Finance |
|---|---|---|---|---|
| Master data alignment | X | X | X | |
| Product listing | X | X | ||
| Vendor number management | X | X | ||
| Store Account Opening | X | X | ||
| Pricing Management | X | X | ||
| Accounts Payable/Receivable | X | X | X | |
| Claims Management | X | X | X | X |
| GS1 membership | X | |||
| EDI management | X | X | X | X |
Back to Contents
Pre-requisites
Electronic Trading terms
- Legal agreement with a trading party to utilise and honour electronic trading instructions and electronic interchange documentation
- Agreement of listed products that will be a part of any electronic trading
- Agreement on the customer stores and subsidiaries that will form part of any electronic trading
- Agreement on receipting mechanisms and transactional artifacts (electronic or manual)
- Understanding of corporate policy and procedure relating to electronic processing of transactional documentation (electronic or manual) and the resultant accounting effect
Back to Contents
Trading partners
Agreement with a trading partner to utilise and honour electronic trading instructions and electronic interchange documentation.
Vendor Numbers
The buyer defined and supplied account number for the supplier. This is often the Accounts Payable account number for that supplier or the specific trading terms. The messaging components carry this number in the avp "code": "BUYER_ASSIGNED_VENDOR_NUMBER"
Receiver and Sender Global Location Numbers (GLN)
Global Location Numbers (GLN) are globally unique identifiers for a party. These numbers resemble barcode numbers and are managed by GS1.
The STF network is based on GS1 standards and as such GLN's are utilised for participant identification on the network.
If you do not have a GLN assigned to your firm or store, please contact the FMCGX Helpdesk who will be able to assist you with the administration for assignment of a GLN by GS1 or a temporary identifier.
Back to Contents
Legal Requirements
- Electronic Trading terms agreement
- Corporate mandated operator of this platform (Administrator)
Back to Contents
GS1 membership and administration
It is highly recommended and encouraged that one becomes and maintains membership with the standards organisation, GS1.
GS1 is the organisation responsible for managing the barcodes and related EAN numbers (GTIN - Global Trade Item Number) that uniquely identify products and their packaging configurations.
The organisation also manages the EAN codes applied to locations known as Global Location Numbers GLN, which are used to uniquely identify transactional parties, as well as perfectly identify delivery and shipping locations. These GLN numbers are extensively used within this API set and so it is requested that the appropriate membership is concluded with the GS1 organisation within you jurisdiction.
The adherence and conformance to GS1 approved and registered codes, eases automation and improves the accuracy, ensuring cleaner transactions and better business.
| Description | Code | Type | Used for | Characteristics | Example |
|---|---|---|---|---|---|
| Unit Barcode | EA | EAN 13 | The Barcode of the smallest saleable unit (consumer unit - eaches) | 13 digits, normally starting with 600 | Barcode on a Soda Can |
| Shrink Barcode | CK | EAN 14 | The Barcode of a bundled pack, often the Intermediate pack making up a case (shrink wrap) | 14 digits normally starting with 16 | Barcode on a 6 pack |
| Case Barcode | CS | EAN 14 | The Barcode on the outer case / carton container (containing shrinks or eaches) | 14 Digits normally starting with 16 | Barcode on the carton box pack of 24 |
Back to Contents
Master data alignment
The term Master data refers to all forms of static and reference data that will be utilised in construction of electronic documentation, identification of products, parties or places and normalises data for processing by all parties.
- Product master
- Customer or Stores master
- Nominated order days / Nominated delivery days
- Vendor account mapping
- Store access groups
- Organisational mapping - Stores to distribution centres - Customers to Key Account Managers - Regions
Back to Contents
Attestation
Back to Contents
Product Listing
Vendor Number Management
Pricing Management
Accounts Payable
Claims Management
Documents
| Business Documents | Technical Documents |
|---|---|
| Orders | Client code |
| Invoices | Service Stack client reference with code-generator(dto's) |
| Claims | Package Managers: NuGet, NPM, Maven |
| [Credit Notes](Business Usage/Transactions) | Microsoft Power Automate (no code) |
| Proof of Delivery | |
| Remittance | |
| [Product master](Business Usage/ProductMaster) | |
| [Listing and deal sheet](Business Usage/Pricing) | |
| Product returns and uplift instructions | |
| Demand assessment |