> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to track orders and the production line
- URL: https://blog.jestor.com/order-management-production-tracking/
- Published: 2026-09-16T18:50:13.000Z
- Updated: 2026-09-16T18:50:13.000Z
- Author: Bruno Bannach

An **order management system** has to answer two questions at once: what the customer ordered, and where that order currently is in production. In **Jestor**, a ready made template covers orders, clients and the production line, with a product registry underneath.

## Why orders and production drift apart

Sales records the order. Production works from a list someone assembled from those orders. The two are copies of each other, and copies diverge.

The customer then asks for a status and nobody can answer without walking to the floor.

What a connected flow fixes:

- Production working from a list that is already out of date
- Order changes that never reach the people making the thing
- No audit trail of who updated a product or a price
- Status questions answered by asking around
- Products registered inconsistently across teams

## What the product registry should hold

| Field        | What it stores                | Why it matters          |
| ------------ | ----------------------------- | ----------------------- |
| Name         | How the product is identified | Searchable by everyone  |
| Code         | Internal reference            | Matching across systems |
| Value        | Current price                 | Order totals            |
| Created by   | Who registered it             | Accountability          |
| Last updated | Date of the last change       | Spotting stale data     |
| Updated by   | Who made the change           | Audit trail on prices   |

## Step by step to run it

1. **Install the orders template**, which is fully customizable.
2. **Register your products** through the form, adding any fields your business needs, such as unit of measure.
3. **Review the product table**, which shows name, code, value and the change history.
4. **Register clients** so orders reference an existing record.
5. **Create orders** linking client and products.
6. **Move orders along the production line**, updating status as work progresses.
7. **Edit products from the card or the table**, whichever is faster in the moment.

## Why the change history matters on products

Price changes are where disputes come from. Knowing who updated a product, and when, turns an argument into a lookup. It also reveals when a price has not been reviewed in a year, which is its own kind of problem.

- **One registry:** sales and production reference the same products
- **Audit fields included:** created by, updated by and update date
- **Editable inline or in the card:** whichever suits the moment
- **Extensible fields:** add whatever your product data requires

## Frequently Asked Questions

### Can I add custom fields to a product?

Yes. The base fields can be extended with anything relevant to your business. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I see who changed a product?

Yes. The registry records who created it, who updated it and when.

### Can orders and production share the same data?

Yes. Both work from the same records rather than from separate lists.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.