SoftwareHow-tosPublished

Building a price list your software can actually use

Most matrices live in a spreadsheet and a person's head. What a system needs to compute a quote, and how to structure it so it stays right.

  • 11 min read
  • 1,043 words
Building a price list your software can actually use — pricing calc at a print shop
Software11 min readA1printsoft EditorialPhoto: Jakub Żerdzicki / Unsplash
On this page6 sections

The short answer

  • Three people quoting the same job should produce the same number — in most shops they do not
  • A computable price has four parts: garment, decoration, per-job costs, and rules
  • Hold per-job costs separately from per-piece ones or small orders will be wrong
  • Encode discretion as a range, not as an open field
  • Test the structure at your smallest and largest quantities before relying on it

Every shop has a price list. Very few have one a system could use, because most exist as a spreadsheet plus a set of adjustments that live in the owner's head — a bit more for that customer, a bit less at this quantity, nothing for setup if they reorder within a month.

Those adjustments are usually sensible. The problem is that they are invisible, so nobody else can apply them and no software can compute them.

Why do quotes vary between people?

Because the rules are not written down. Ask three people in a shop to quote a 48-piece two-colour front and you will frequently get three answers, and each will be defensible.

That variance costs money in both directions. Quoted low, you win work at a margin you did not intend. Quoted high, you lose work you wanted. And because nobody records which happened, the pattern never becomes visible — which is why quote-to-order rate is worth tracking alongside the quotes themselves.

Making the price computable is not about removing judgement. It is about separating the parts that are arithmetic from the parts that are judgement, so the arithmetic stops being re-done and re-argued.

The four components

ComponentScales withExample
GarmentQuantityBlank cost at your supplier break
Decoration per pieceQuantityRun time, ink, spoilage allowance
Per-job costsNothingScreens, makeready, digitising, art
Rules—Minimums, breaks, rush, reorder discount

The third row is the one that has to be modelled separately, and it is where systems most often go wrong. A price list that bakes setup into the unit price cannot compute a small order correctly — setup does not shrink, so spreading it across a per-piece figure misprices both ends of the range.

Hold it as a per-job line and the arithmetic works at any quantity: total = per-job costs + (per-piece costs × quantity), then margin, then rules.

Structuring it so it stays right

Model the things that actually vary, rather than writing out every combination. A matrix of every garment against every decoration against every quantity is unmaintainable — one supplier price change means editing hundreds of cells, and it will not get done.

Hold these separately

  • Garment costs, from the supplier, at their own breaks
  • Decoration rates by method, colour count and print size
  • Per-job charges — screens per colour, press setup per location, digitising
  • Quantity breaks as a rule applied to the result, not baked into every line
  • Margin as a separate figure you can change in one place

Structured that way, a supplier price rise is one update rather than a rebuild, and a margin decision is one number rather than a week's work. That is the practical difference between a price list that stays current and one that quietly goes stale — which is the usual reason a shop is underpriced without deciding to be.

Holding it in the system everyone quotes from, rather than in a file one person maintains, is what makes it stick. That is what the quoting side of our back-office management is for.

If a supplier price rise means editing hundreds of cells, it will not get edited.

Rules and exceptions

Encode the rules; bound the exceptions.

RuleEncode as
Minimum orderA quantity floor with a message
Quantity breaksThresholds applied to the computed total
RushA percentage or fixed uplift, by lead time
ReorderSetup reduced when artwork is on file
Contract pricingAn account-level rate
Salesperson discretionA discount range, not an open field

The last row is the one that keeps a price list meaningful. Discretion within a stated band is a commercial tool; an open discount field means your list is advisory and your actual prices are unknown.

Where a genuine exception is needed beyond the band, make it require approval and record the reason. Six months of those records tells you whether the exceptions are individual or whether your list is wrong in a specific place.

Keeping it current

Review on a schedule rather than in reaction to a supplier email. Blanks move, wages move, and a list left alone for two years has taken a real-terms cut nobody agreed to.

A review cadence

  • On supplier notice: update garment costs, check affected margins
  • Quarterly: compare your landed cost against the list price for the top ten garments
  • Annually: rebuild a standard job from measured costs; review minimums and setup
  • After any process change: re-time makeready and run rates

The quarterly landed-cost check is the one that catches quiet erosion. Your list uses the garment price you loaded; what you actually pay includes freight and any broken-case charges, and the gap between the two is margin disappearing without a decision.

Testing before you trust it

Once configured, quote your own known jobs and compare against what you would have charged. Differences are informative in both directions.

The test set

  • Your smallest realistic order — does it cover per-job costs?
  • Your most common order — does it match what you charge today?
  • Your largest — is the margin still acceptable?
  • One piece either side of every break — does the total ever fall as quantity rises?
  • A reorder — is the setup reduction applied?
  • A rush job — is the uplift applied?

Run the test set again after every structural change, not just at setup. A margin adjustment or a new quantity break can reintroduce a defect that was fixed months earlier, and the only way to know is to re-run the same jobs and compare.

The break test is the one that catches the defect customers find first. If ordering more ever costs less in total, the breaks are placed wrongly, and a system will apply that error consistently rather than occasionally. The rest of the software archive assumes your prices are computed rather than recalled.

Filed underSoftwareHow-tos
Share
Written byA1printsoft Editorial
175 articles

The print production desk at A1Printsoft. Writes the practical side of running a decorating shop: what things cost, how long they take and what to charge, checked against published trade figures.

Keep reading

More on software

All Software articles

Set up in an afternoon. From what you already do.

Free for 14 days · no card · pick what you make and we preload the methods, products and price tables.