updated as of: October 30, 2014
last author: Andy Theuninck
The installation script for IS4C also servers as a configuration page. It's broken into several sections with tabs along the top. Necessities, which is the bare minimum to get a lane up and running.



Extras is a bit of a catch-all. It contains settings related to hardware, membership, the lane user interface, and tenders.


Receipt contains settings for printing and formatting receipts. Using the modular receipt is highly recommended as it provides the most flexibility for store-specific customizations.


Scanning contains settings related to handling UPCs as well as departments that have special significance.


Security controls what functionality requires a manager password.


Debug has some information about logging and a couple developer settings.

DB Updates

DB Updates is exactly what it sounds like. Schema changes can be applied from this page.

Sample Data

This page lets you load employees, customers (custdata), products, and departments. Customers and products are the only items strictly necessary to get going. There is a training login number, 9999, built into IS4C. Departments don't actually have to exist at the register unless you're doing open rings.

Behind the scenes - Where is this stuff stored?

By default, a small number of settings are saved in ini.php. Everyting else is stored in a database table named parameters on the lane. This table is in the operational database (default name opdata). The following settings are always stored in ini.php and only in ini.php:
  1. Lane Number
  2. Store Number
  3. Lane Database Host
  4. Lane Database Type
  5. Lane Database User Name
  6. Lane Database Password
  7. Lane Database Operational DB
  8. Lane Database Transaction DB
  9. Special Department modules (on the Scanning tab)
The first eight settings are required to connect to the database and access the paramters table. The other has a convoluted structure that cannot currently be stored in the database.

When the lane loads, it reads settings in this order:

  1. ini.php
  2. parameters table records with lane_id zero
  3. parameters table records where lane_id matches that specific lane
All settings can be stored in ini.php if preferred, however if the setting is stored in both ini.php and the parameters table with different values lane behavior can be unpredictable as the differing values periodically overwrite one another. The web-based configuration pages will attempt to update settings that are present in ini.php. The Necessities tab will also attempt to detect any discrepancies between ini.php and the parameters table.