CATALOGUE, UNITS AND PRICE LISTS

Your products, your units, your prices. Applied the same way every time.

Load your SKUs, the units you sell them in and your price lists once. Every order line is priced from them by rules, not from memory and not by the AI.

Taking pilot customersThe Orders module is being built into KeelSG now, and we are taking pilot customers. The Customers module is available today.

01Right price, every line
02Units that convert
03Prices frozen on confirm
Where the line is

“Prices are picked in a fixed order: the customer's own price first, then their tier price, then your default price. The AI reads the order. It never sets a price, changes one, or creates a product.”

What you actually get

6 things.

And what each one is for.

  1. SKUs, and the names customers use

    Each product has a code and a description. The names your customers actually use, such as "the 5kg rice", are saved as aliases so they match next time. A name that could mean two products is flagged for a person to choose.

    Benefit The catalogue learns your customers' words without guessing.

    Covers: SKU codes · aliases · ambiguous names flagged

  2. Units of measure that convert

    Sell the same product by the carton, the pack or the piece, each with its conversion to the base unit. A line ordered in a unit that product is not sold in is flagged rather than guessed.

    Benefit "2 cartons" and "48 pieces" come out as the same thing when they are.

    Covers: Base unit · selling units · conversion factors

  3. Tier prices and customer prices

    Set a default price, prices for customer tiers, and prices for a single customer, each with the dates they apply. Two prices for the same thing at the same level on the same dates are refused when they are entered, and the clash is named.

    Benefit Special prices stop living in one person's head.

    Covers: Default · tier · customer · effective dates · clash refused

  4. Import with a preview

    Load products and prices from a spreadsheet. Before anything is saved you see which rows will go in, which are rejected and which clash with prices you already have. The import saves every row or none of them.

    Benefit A bad row cannot half-load your price list.

    Covers: Preview · rejected rows · clashes · all or nothing

  5. Confirmed orders keep their prices

    Once an order is confirmed, its lines, units and prices are frozen. Changing a price list next month changes future orders, never ones already agreed.

    Benefit A price change does not rewrite what a customer already agreed to.

    Covers: Price snapshot on confirmation · unchanged by later edits

  6. Totals worked out by rules

    Unit conversions, line prices and order totals are calculated by fixed rules, never by the AI, and totals in different currencies are never added together. Receipt notes show totals but are not tax invoices.

    Benefit The arithmetic is the same every time, and you can check it by hand.

    Covers: Rule-based pricing · per-currency totals · no AI arithmetic

How it runs

Four steps, in this order, every time.

  1. 01

    Load

    Import products, units and prices, with a preview first.

  2. 02

    Group

    Put customers into tiers on their customer record.

  3. 03

    Price

    Each line takes the customer, tier or default price.

  4. 04

    Freeze

    Confirmation locks the price the customer agreed to.

30
The next step

Thirty minutes, and you leave with three answers.

Whether a pilot fits the way your orders arrive, what we would set up, and what it would cost. Written down, so you can put it in front of a partner or a board.

Bring three things

  • A few real orders, as they arrive today.
  • Your product and price list, in whatever form it is in.
  • Who takes and confirms orders now.

Leave with three answers

  • Whether the pilot fits.
  • What we would set up, and how.
  • What it would cost, written down.