FiscalityOne – Scanned Barcoded Goods-In & Customer Dispatch

Introduction

Fiscality:One provides tightly integrated barcoding functionality to enable users to quickly and accurately record goods-in from suppliers and the production line, without the need for much manual input other than the input of a purchase/works order number and quantities.  The interfaces are designed for touch-screen input and do not require a mouse; only a number-pad keyboard is required for inputting quantities.  This same touch-screen/number-pad approach is taken throughout most of the barcoding software to ensure ease of use and to eliminate the need for complex user input – ideal for industrial and manufacturing environments.

Barcode Labelling (Additions to Stock)

  • Stock is added to the database via Product Additions and uniquely numbered barcode labels can be printed and placed on each product/pallet or box as they arrive from both suppliers and the production line (raw materials and finished goods) – both are additions into stock.
  • Each barcode is a unique record in the database and linked to a location (which is linked to a site).
  • Each barcode is created against an Purchase or Works order and has a quantity of greater than or equal to one.
    • Depending how stock is stored in the warehouse, then split for production and shipment, Fiscality:One allows the creation of barcodes for any quantity, i.e. 125, that shows the barcode has 125 of that product within.
  • When you create an addition for finished goods on the production line, Fiscality:One will automatically minus the raw materials stock based on the Product’s Components (Bill of Materials / BOM).
  • Read more about compatible hardware (scanners and printers).

Scan Sessions

  • As each barcode is uniquely numbered, it can be scanned any number of times during the scanning process, and depending on how the Scan Session Type has been configured, Fiscality:One will correctly process and group the downloaded data.  Any anomalies will be highlighted to the user.
    • Only when multi split quantities for the same barcode have been entered will it change the multiple-scan behaviour, and even then the only the count or sum quantity of splits will be recorded when downloaded into the same Scan Session.
  • There are various type of Scan Session, for example, Customer Shipment, Stock Movement, Stock Adjustment, Stock Deletion
  • Barcodes are downloaded into Fiscality:One via individual Scan Sessions, which comprise one or more scanned barcodes.  These Scan Sessions are very useful for separating the activity of different users and of different Scan Session Types (Shipment, Movement, Adjustment etc).
  • Scan Sessions can be left active and unfinished as required.
  • Various checks are performed for each type of Scan Session and any errors are highlighted to the user, preventing the Scan Session from being finished until all have been cleared.

Shipment to Customers

  • Customer Orders in Fiscality:One are termed Requirements, and these form the picking sheets for used in order fulfilment.
  • As the user picks the items required for the Customer’s Order, they scan each barcode and once finished, download the scanner into a Shipment Scan Session.
  • Fiscality:One will optionally attempt to match the scanned barcodes (Products and quantities) to one or more Customer Orders (Requirements).  If no Requirement(s) are manually entered by the user, Fiscality will attempt to match globally to open Requirements within the automated criteria defined by the system.
  • If all scanned items have been matched successfully, the user will be able to complete the Shipment Scan Session and produce Delivery Notes, which can be sent with the Shipment’s transport and either attached to the package or handed to the customer upon delivery.
  • If any scanned items cannot be matched to an existing open Requirement, these will be highlighted to the user, and the erroneous items must be removed or corrected before the Scan Session can be finished:
    • it might be that an item has already been shipped to the Customer by another user…
    • perhaps the quantity was incorrect (either too less or too many were picked)..
    • as is often the case, the wrong item was picked by mistake…