Information and description
Subscribers can receive their agreed net prices via Finfo. Customer-specific files can be sent either to a retail chain or to an individual store. If a supplier has an agreement with a chain and sends customer-specific prices to them, all chain members will receive the agreement, which then only needs to be reported once.
Instruction
Customer-specific price information can be delivered in two ways:
-
As a text file with fixed field lengths, according to file specification
-
As a text file (CSV), created from a dedicated Excel template
The file can contain both discount records and net prices at the article level. In Level 2, net prices can also be specified at the packaging level.
Detailed information about file formats:
Files are uploaded in the Finfo portal or sent to Finfo via FTP. Login credentials are provided by Finfo Customer Support. More information about FTP can be found here: FTP Transfer Instructions.
Customer and contract ID
Each customer-specific file must include a customer ID and a contract ID, which must always be entered the same way each time updated prices are sent to the customer.
The first time a customer-specific agreement is to be sent to a customer via Finfo, a customer ID for that customer must first be registered in the Finfo portal. You may use the same ID as in your own business system, provided it fits in the field.
File control and distribution
Customer-specific files from suppliers are received and automatically checked. A file containing errors or in the wrong format generates a response email to the supplier, describing what needs to be corrected. The file must then be corrected and resubmitted.
An approved file is distributed to the receiving customer during the night before the next day, unless a future distribution date has been specified.
A message to the customer can be included in the text record. This message will be distributed together with the price information as a separate document.
Price information
The net price of an article always applies before any discounts – in other words, a price record always takes precedence over a discount record.
If the customer-specific file contains prices for articles that have not yet been registered in Finfo’s database, the submitted net prices are stored and distributed to the customer as soon as the articles have been imported into Finfo’s database.
When making changes to the agreement, you may choose to send either the entire agreement or only new/updated records.
Dates
The field Activation date in the contract record refers to the distribution date and applies only the first time the agreement is submitted. The activation date should be at least two weeks earlier than the price effective date, so that the subscriber/retailer receives the new agreement in time for import, calculations, etc., in their local POS system.
If the agreement should be distributed immediately, you can enter 00000000 (eight zeros) instead of a date.
For future price adjustments, the Effective date field is used after each article number in the price record or packaging price record (Level 2).
Agreement information can be changed as often as needed. Future known price changes can also be entered well in advance. The new information will be distributed the same evening that the distribution date occurs.
There may be several detail records for the same article/discount code but with different prices and distribution dates. These are applied in chronological order — when the distribution date for a record occurs, the agreement with the new net price is sent out.
If an End date other than 99999999 is entered in the contract record, both parties to the agreement will receive a notification 20 days before the agreement expires. If the agreement is to be renewed, updated prices must be submitted before the expiration date.