Skip to main content
GullySystem
A practical guide

Software for a stamping shop: custom build or ready product

Ganesh HSStrategy and Technology, GullySystem
Practical advice · 5 min read

In this guide 6 sections
The short answer

Buy a ready product. Choose it when your shop runs standard job travelers, coil receipts, press scheduling and die maintenance logs without odd exceptions to any of them. Build custom when progressive die costing, skeleton credit against the coil or customer owned tooling rules fit no catalogue on the market. Most shops start ready. A custom layer follows.

Start with what a stamping shop actually records

Write down every record. Coil receipts carry heat number and gauge, job travelers carry part number, and the press log holds tonnage, strokes per minute, die repair tickets and scrap weights. Most of it is common.

A ready product covers those common records well, because many shops have pushed it into shape over the years and the die history screen arrives finished on day one. Nobody has to guess the layout.

The question is the leftover. List three records no catalogue would think of, such as skeleton weight returned for credit, stroke count against a customer’s limit and a plating vendor’s lot number. Those few settle it.

  • Coil receipt with heat number, width, gauge and weight
  • Job traveler tied to part number and die number
  • Press log with stroke count and downtime reason
  • Die repair and sharpening history
  • Scrap and skeleton weight per job

Where a ready product usually fits

A ready stamping product fits when you buy coil, run jobs across a handful of presses and ship against customer purchase orders with agreed delivery windows. Quote, traveler, inspection and invoice follow one known order, so setup takes weeks and not months, with a vendor trainer showing the press operators each screen.

It also fits a small shop where nobody can own a custom system, because the vendor fixes bugs while a build needs a person to look after the code. Staff time is the limit.

Be wary of demos that skip the die side. Ask for strokes since last sharpening on a die history screen, then watch whether the salesperson opens it or changes the subject. A product that cannot show it was built for general job shops with no dies to track, so walk away.

Where a custom system pays off

Progressive dies change the costing. Cost per part depends on pitch and skeleton credit, because one strip feeds several stations and a single hit makes a finished part, a carrier and slugs.

Few products model that. Customer owned tooling is another trigger, because the customer owns the die while you hold it, and you must count strokes against their life limit and report back. A build enforces it on every job.

Outside processing is a third trigger. When stamped parts go to tapping, plating and kitting at three different vendors, a ready product forces awkward workarounds that operators quietly abandon within a few months.

  • Progressive die costing by pitch and strip utilisation
  • Scrap and skeleton credit returned against the coil lot
  • Customer owned tooling with a stroke life limit
  • Outside process routing for plating or heat treat
  • Customer portals with their own part approval steps

The hybrid path most shops take

Few shops need everything built. A common route is a ready product for orders, inventory, quality and invoicing, with a small custom module for die tracking that reads part and job numbers.

The risky part stays cheap. If the custom die module turns out wrong, you replace only that module, and the orders, coil lots and invoices in the ready product carry on untouched.

Ask each vendor how the product exposes data. A product that lets you read jobs, parts and coil lots through an API or a clean export makes a good base for later additions. A closed one locks you in.

A decision test you can run this month

Take your ten most recent jobs and trace each one on paper from coil receipt to shipped carton, marking every step that a candidate product could not record. If fewer than three steps are marked, buy.

Marks clustered on die life and cost per part point to a small build around those two records, with the ready product handling everything else on the sheet. Marks everywhere mean a process problem.

Bring the marked sheets to every vendor meeting. Make each vendor show those exact steps on screen, using your own part numbers and one real coil lot, then note who answers and how quickly.

Stamping shop software decision sheet

Three columns hold the record, the ready product result and the custom need, against rows for coil receipt, job traveler, press log, die history, scrap credit and tooling ownership. Each cell reads covered, partial or missing. The last box states buy, hybrid or build.

Open a blank worksheet to print

Questions owners ask

How much of a stamping shop can a ready product cover?

Orders, inventory, travelers, inspection and invoicing are usually covered, while die life tracking and progressive costing are the common gaps that a catalogue demo skips. Test both with your own part numbers.

Can we add die tracking later?

Yes, provided the product exposes jobs and parts through an export or an API, so get that promise in writing before signing. A closed one means keying die data twice.

Who should own a custom stamping system?

Someone inside the shop must own the requirements, and the production manager or quality manager is the usual choice because both read die repair tickets and scrap reports. The vendor supports the code. The shop decides what a die record contains.

Is a spreadsheet enough for coil costing?

For a few repeat parts, yes. It breaks once strip layouts change for each customer and nobody trusts the formulas any longer, and that is the moment to move costing into a system.

Browse all guidesBack to top ↑
Next step

Have a specific situation to work through?

This article covers the general case. Tell us what you’re actually dealing with and we’ll respond directly.

Share Your Requirements