General information
Subscribers, i.e. the customers or retailers who receive your article data from the Finfo database, can receive their agreed prices through Finfo.
In this documentation, we use the term subscriber for this receiving party.
Customer-specific price files can be provided either to a retail chain or to a single store. If a supplier has an agreement with a retail chain and uploads customer-specific prices to the retail chain's central subscriber account, all retail chain members will receive the agreed prices. The prices only need to be reported once.
There is often a need to provide several different customer-specific price files to the same subscriber, depending, for example, on ordering behaviour in terms of quantity and frequency (volume), price tariffs regulated by agreements, as well as geographical conditions and freight terms.
The different price files are identified using the Agreement ID (Avtals-ID), which identifies each price list.
The price files can contain net prices and discount entries or customer-specific recommended sales prices.
Files are uploaded to the Finfo Portal or submitted to Finfo via an FTP programme. Login details are provided by Finfo Customer Support.
More information about FTP can be found here: FTP transfere instructions.
How customer-specific prices work
In the customer-specific price file, you can enter discount entries per discount group and customer-specific prices per article number. You can also enter customer-specific prices at packaging level by specifying the GTIN for the relevant packaging. The specified GTIN must then be registered for the relevant article in Finfo database.
If a discount rate is entered in the price file, a net price is calculated based on the stated base price for the article minus the discount rate. The calculated net price is distributed to the subscriber.
If both a valid net price and a discount exist for an article in the price file, the net price is always used. The system first looks for a net price for the article and then applies any discount if no net price is available. A price entry therefore always takes precedence over a discount entry.
The type of prices expected in the price file may vary and should be agreed with your subscriber.
For example, these may be:
-
agreed net prices
-
customer-specific recommended sales prices, or
-
other prices
As a subscriber, you will often expect invoice matching to be accurate to the penny when using customer-specific net prices. However, price information can also be used for different pricing strategies or as a basis for setting shelf-edge prices. We therefore recommend confirming with the subscriber which prices are expected in the price file(s), and whether more than one Agreement ID (Avtals-ID) is needed to meet the subscriber's requirements based on your agreement.
Customer-specific price information can be submitted in two different ways:
-
Excel file using a specific template – Find and download template here
-
Text file with fixed field lengths, according to the file specification – this option is only used by existing suppliers who already submit customer-specific price information in this way.
Files are uploaded via the Finfo Portal or via an FTP programme. The prices are then distributed to the intended subscriber.
If the customer-specific price file contains prices for articles that have not yet been registered in the Finfo database, the uploaded prices are saved and distributed to the subscriber as soon as the articles have been registered in the Finfo database.
When making changes to the price list, you can choose to submit the entire price list or only new or changed entries.
Price list information can be changed as often as needed. You can also enter known future changes as far in advance as you like. The new information will be distributed on the same evening that the distribution date occurs.
There may be several detailed entries for the same Article/Discount Code, but with different prices and distribution dates. These are applied in chronological order, so that when the distribution date for a detailed entry occurs, the price file is distributed with the applicable new net price.
File validation and distribution
Customer-specific price files submitted by suppliers are received and automatically checked by Finfo's systems. A file containing incorrect information or an incorrect format generates a reply email to the supplier with information about what needs to be corrected. The file must then be corrected and submitted again. The system does not assess the prices entered.
An approved file is distributed to the subscriber overnight, unless a future distribution date has been specified.
How to fill in the price file
All fields in the price file must be formatted as text.
Avoid any other type of formatting, such as currency, percentage or number formatting.
A customer-specific price file can contain several different types of entries. The different entries and the information to be entered in each entry are described below.
Agreement entry (Avtalsposten)
The Agreement entry is the header containing the price list's identification and validity information and is the only entry that is always mandatory.
The Agreement entry is only updated for an existing price list when correcting the Valid through date (when closing or extending the price list).
Each customer-specific price file must contain a Customer ID (Kund-id) and an Agreement ID (avtals-id), which must always be entered in the same way each time you upload updated prices to the subscriber.
The fields included in the Agreement entry, with mandatory fields marked:
Avtals-ID (Agreement ID):
Your identifier for the prices covered by the price file. Maximum 20 characters.
Finfos Leverantörs-id (Finfo Supplier ID):
Your supplier number at Finfo. Maximum 12 characters.
Kund-ID (Customer ID):
Your identifier for your subscriber, for example their customer number in your business system.
This tells Finfo's systems which subscriber account should receive the prices in the customer-specific price file.
The Customer ID is always the same for the same subscriber, regardless of which price list (Agreement ID) is uploaded.
Maximum 15 characters.
Registered for the intended subscriber in the Finfo Portal.
Aktiveringsdatum (First Activation date):
The date on which the price list is activated and distributed to the subscriber for the first time. This should be entered well in advance of the date on which the price list takes effect.
Enter as YYYYMMDD. If you want the information to be distributed immediately, enter 00000000.
This field must not be changed afterwards.
Gäller till och med datum (Valid through date):
The date on which the Agreement ID (Avtals-ID) itself is to be closed. Enter as YYYYMMDD.
This rarely reflects how long the prices are valid, as prices with new effective dates are updated in the Price entry/Packaging price entry.
When the specified date has passed, the article information is distributed to the subscriber without the customer-specific prices/discounts associated with this Agreement ID. Both parties are notified 20 days before the Agreement ID is closed.
Enter 99999999 if the Agreement ID is valid indefinitely. This field is only updated when the Agreement ID is closed or extended.
Ansvarskod (Responsibility code):
Indicates who is responsible for and updates the price list.
L = Supplier
A = Subscriber
K = Retail chain
Ansvarig abonnent (Responsible subscriber):
Only entered when the Responsibility code (Ansvarskod) is "K".
The retail chain's ordering number at Finfo.
Avtalstyp (Agreement type):
Indicates which type of customer-specific price the price list contains.
N = Net price (most common)
C = Recommended sales price / shelf-edge price
Renskod (Clearance code):
Used when previously entered information in the price list is to be removed from the database.
Blank = no clearing.
P = removes all currently valid Price entries that are not included in the current price file.
R = removes all currently valid Discount entries that are not included in the current price file.
A = removes all currently valid Price and Discount entries that are not included in the current price file.
Kod för gällandedatum (Effective date code):
To specify from which date prices are valid in, in the Price entry or Packaging price entry, enter J in this field. Recommended.
Agreement entry example:
Price entry (Prisposten)
This is where you enter the prices you want to provide to the subscriber.
The price is entered per the base price unit with which the article is registered in the database.
The Price entry is updated when new prices have been agreed and/or when new articles are added.
When updating a price, update the existing row with the new price and effective date.
New articles are added on a new row. Remember to also register new articles in the Finfo database.
If the Agreement type in the Agreement entry is N, enter customer-specific net prices in the Price entry.
If the Agreement type in the Agreement entry is C, enter customer-specific recommended sales prices in the Price entry.
It is recommended that the Price entry is updated well in advance of the date on which the new prices take effect, so that your subscriber has time to check, plan and prepare the information in their business system.
The fields included in the Price entry, with required fields marked:
Artikelnummer (Article number):
Your article number.
Enter it exactly as registered in the database.
Maximum 18 characters.
Pris (Price):
The price you want to provide to the subscriber according to the base price unit.
Enter with two decimal places.
Distributionsdatum (distribution date):
Only enter this when the information should not reach the subscriber immediately.
Enter the date on which you want Finfo to distribute the information to the subscriber.
Enter as YYYYMMDD.
Gällandedatum (Effective date):
Recommended.
Enter the date from which the prices are valid.
Enter as YYYYMMDD.
Update this field when the price is updated.
Price entry example:
Text entry (Textposten)
In the Text entry, you can write a message to the subscriber.
This message is distributed together with the price information as a separate document.
Updated when needed.
The fields included in the Text entry, with required fields marked:
Text:
Enter the text you want to provide to the subscriber.
Maximum 45 characters per line.
Radnummer (Line number):
The order of the lines within the same date.
Distributionsdatum (Distribution date):
Only enter this when the information should not reach the subscriber immediately.
Enter the date on which you want Finfo to distribute the information to the subscriber.
The date should correspond to the distribution dates for the other entries if the Text entry is to be distributed at the same time as these.
Enter as YYYYMMDD.
Text entry example:
Packaging price entry (Förpackningsprisposten)
If the subscriber requests a price per package using GTIN, instead of a price per article and base price unit, use this section of the price list instead.
This section should only be completed when the subscriber has explicitly requested a price per package.
Leave the Price entry empty if you use the Packaging price entry.
It is recommended that the Packaging price entry is updated well in advance of the date on which the new prices take effect, so that your subscriber has time to check, plan and prepare the information in their business system.
The fields included in the Packaging price entry, with required fields marked:
Artikelnummer (Article number):
Your article number.
Enter it exactly as registered in the database.
Maximum 18 characters.
Pris (Price):
The price you want to provide to the subscriber according to the base price unit.
Enter with two decimal places.
GTIN:
The GTIN linked to the relevant packaging.
This GTIN must be registered in the Finfo database for the relevant packaging and article.
Maximum 14 characters.
Distributionsdatum (distribution date):
Only enter this when the information should not reach the subscriber immediately.
Enter the date on which you want Finfo to distribute the information to the subscriber.
Enter as YYYYMMDD.
Gällandedatum (Effective date):
Recommended.
Enter the date from which the prices are valid.
Enter as YYYYMMDD.
Update this field when the price is updated.
Packaging price entry example:
Discount entry (Rabattposten)
The Discount entry can be used when you want Finfo's system to calculate a net price to be distributed to the subscriber.
The system uses the registered base price for the articles included in the discount group and deducts the discount rate specified in the price file from the relevant articles.
When the base price for an article is updated, a new net price is calculated for the subscriber.
Please note that you cannot control the date from which the discount rate, and therefore the calculated net price, takes effect.
If the subscriber is to receive updated net prices on a date other than the date on which a general base price adjustment takes effect, we recommend using the Price entry instead.
The fields included in the Discount entry, with required fields marked:
Rabattgrupp (Discount group):
Enter the discount groups you have registered for your articles in the database.
Maximum 5 characters.
Rabattsats (Discount rate):
Enter the discount rate to be deducted from the base price.
Enter with two decimal places.
Distributionsdatum (distribution date):
Only enter this when the information should not reach the subscriber immediately.
Enter the date on which you want Finfo to distribute the information to the subscriber.
Enter as YYYYMMDD.
Discount entry example:
