Skip to content
English
Raise Request Customer portal
  • There are no suggestions because the search field is empty.

Import Price Changes

Back Office - How To

This outlines How To Import Price Changes into Back Office.

 

Subjects?      ▲ ▼

 

About      ▲ ▼

 

What Is Required?      ▲ ▼

  • Swiftpos v10+
  • To ensure accuracy, imported Price Changes should always be reviewed in the Price Changes Wizard before being applied.

 

What Is Supported?      ▲ ▼

  • The Price Changes Wizard currently supports the following:
    • Import prices from CSV (PLU)
    • Import prices from CSV (Barcode)
    • Import prices from XML (PLU)
    • Import prices from XML (Barcode)
    • Import From PDT File

 

Notes ...

 

The Import From PDT File option is only available when the Venue is registered for Fuel.

 

What To Consider?      ▲ ▼

  • Exporting item/product barcodes to XML is NOT the reverse of the importing of prices from XML. The Export Product Barcodes to XML option generates a different XML structure, which is intended for Product/PDE data. The export file generated, CANNOT be imported using either the:

    • Import Prices from XML (PLU) option

      OR
    • Import Prices from XML (Barcode) option
  • If the Cancel option is selected during a long import, the process may not stop immediately if it has already been started.

 

When Is It Used?      ▲ ▼

Price Changes can be imported into Swiftpos to update the selling prices of a large number of items/products. This process allows for the preparation of the price updates in external files (CSV or XML) and loads them directly using the Price Changes Wizard for review before they are applied.

 

File Formats      ▲ ▼

 

CSV File Format      ▲ ▼

The file can have any name but must be in a CSV format and have an extension of either CSV or TXT. The CSV file must comply with the format outlined below.

 

Notes ...

 

Do NOT include a header row in your import file. If a header row is included, an error will be encountered when importing.


Column

Content

Description

1

Price Level

The Swiftpos Price Level number (e.g., 1).

2

PLU / Barcode

The PLU when using the PLU import, or the Barcode when using the Barcode import.

3

New Price

The new selling price to be applied.

4

Date (Optional)

An optional date for the price change. The date is validated during the import process. It is recommended to omit this date, unless of course it is required by the 3rd party application generating the CSV file.

 

IMPORTANT

 

The imported date does NOT override the Price Change Date entered in the header section of the Price Changes Wizard screen. The Price Change Date must be set.

 

PLU Example

1,1203,4.85 1,1204,6.40 1,1205,8.00

 

Barcode Example

1,9320000503525,6.40 1,9325528003175,8.00 1,93302036,7.80

 

XML File Format      ▲ ▼

The XML import options expect the import file to comply with the Swiftpos Price Change XML structure containing the required PRCHECK data.

 

How To?      ▲ ▼

 

How To GET STARTED?      ▲ ▼

  • Review About and ensure the steps outlined HERE are addressed.
  • Navigate to the Tools menu by selecting the Tools option in the footer section of the Price Changes Wizard screen.
  • Select the appropriate option from the Tools menu.

 

How To Import A CSV File?      ▲ ▼

  • Select from the Import Prices from CSV options available to import a comma-separated values (CSV)) file. The options available are:

    • PLU - Select if the 2nd field in the CSV file is a PLU number.

    • Barcode - Select if the 2nd field in the CSV file is a barcode.
  • Once selected, locate and select the CSV file to be imported. Refer HERE for file format information.
  • Once imported refer HERE to complete the process.

 

How To Import A XML File?      ▲ ▼

  • Select from the Import Prices from XML options available to import an XML formatted file. The options available are:

    • PLU - Select to locate and match items/product based on their PLU.

    • Barcode - Select to locate and match items/product based on their barcode.
  • Once selected, locate and select the XML file to be imported. Refer HERE for file format information.
  • Once imported refer HERE to complete the process.

 

How To Import Fuel / PDT Price Change Import?      ▲ ▼

 

Notes ...

 

This section is only applicable to Venue's that are registered for Fuel.

 

  • It is important to note that when Venues are registered for Fuel and the Price Changes Wizard screen, is opened:
    • The wizard can automatically create a new price change and import the TPRODUCT_PRICE_CHANGE.txt file if it is available and correctly formatted. The TPRODUCT_PRICE_CHANGE.txt file is located in the the configured Fuel uploads folder.
    • This occurs as the Price Changes Wizard screen loads, without the user needing to manually select the Tools option in the footer section of the Price Changes Wizard screen.
    • The prices are imported into the Price Level currently configured in the Wizard.
    • Successfully processed TPRODUCT_PRICE_CHANGE.txt files can be deleted automatically after import.
  • Once imported refer HERE to complete the process.

 

How To Complete The Importing Process?      ▲ ▼

Once the pricing data has been imported into the grid, do as follows:

  • Review the items/products and ensure all have been imported.
  • Confirm and verify the Price Levels to which the price changes will be applied are correct.
  • Check the New Price column contains the correct value for all items/products.
  • In the Price Changes Wizard screen:
    • In the header section:
      • Enter an appropriate name in the Price Change Name field for the pricing change. For example, Summer Price Increase.
      • Ensure the Price Change Date is set to the date the prices should go live.
      • Select the Hold Price Change option if the price changes are NOT to be applied immediately.
    • In the footer section:
      • Select the Save/Commit option to complete the change.
  • Any PLUs or Barcodes that CANNOT be matched to an item/product in Back Office, will be reported in a error logs generated at the end of the import.
  • Duplicates of items/products + Price Level combinations encountered in the imported files will be ignored.

 

End of article      ▲