EDGEBIC Status Lifecycles Explained: What a Quote, an Order, and a Job Each Mean

EDGEBIC by User Solutions runs three status lifecycles that hand off to each other: a quote's, a sales order's, and a manufacturing job's. Status in each is not a label somebody keeps tidy. It changes what the system counts, what it schedules, and what it ignores, which is why the values are worth knowing precisely.

The general concept is covered in what is job status in manufacturing scheduling. What follows is what each value actually does here.

The Job Lifecycle

A manufacturing order carries one of seven statuses.

The pattern to notice is which of these anybody chooses.

In progress, completed, and delayed are derived. They follow from facts recorded elsewhere: an actual start exists, an actual end exists, a date has passed. Nobody sets them and nobody should have to. If one of them looks wrong, the fix is in the actuals or the dates behind it, not in the status.

On hold and canceled are decisions. These are the two a planner genuinely sets, because no fact in the system can tell you that the customer paused the program or pulled the order.

Satisfied from stock is a system outcome with real teeth. It records that the job's demand was fully met from finished goods on hand, so no work center operations were scheduled and only an inventory issue was posted. Keeping it distinct from completed is what stops jobs that consumed no capacity from being counted as evidence of capacity performance, and it is a small but genuine safeguard on any throughput or on-time number you derive later. It exists because EDGEBIC supports make-to-stock alongside make-to-order.

Delayed Is a Warning, Not a State

Delayed deserves separate attention because it is the status most often argued with.

It means exactly one thing: the scheduled end has passed and the job is not marked complete. Two very different situations produce it. A genuinely late job, and a job that finished on time whose last operation was never closed out.

The second is more common than most plants expect, and it is corrosive. A shop with a habit of leaving final operations open accumulates fictional delayed jobs, people learn that the delayed count is unreliable, and then the genuinely late jobs stop being noticed too. The check is quick: look at whether the final operation has an actual end before you go asking the floor what happened.

Operations Have Their Own Status

The job is one level. Underneath it, every scheduled operation carries its own status, derived from its dates: completed, in progress, ready to start, or scheduled.

Ready to start is the one worth pointing out. It means the operation's scheduled start time has arrived and no actual start has been recorded, which is a much more actionable signal than a supervisor scanning a Gantt for bars that overlap today. It is the natural basis for a dispatch view: these are the operations that should be running and are not.

Reading the two levels together is how a partially built job stays legible. Job in progress, operations one and two completed, operation three ready to start, operations four and five scheduled: that is a sentence, not a percentage.

The Sales Order Lifecycle

Sales orders run their own five values: draft, confirmed, shipped, closed, canceled.

Only one of them changes planning behavior, and it changes it decisively. Lines on confirmed orders count as firm demand for the inventory projection and the master production schedule. Draft orders do not. Shipped, closed, and canceled orders drop out because the requirement is no longer outstanding.

That single rule is what lets a sales team work normally without distorting the plan. Provisional orders, conversations that may or may not land, and orders waiting on a customer signature can all exist as drafts without pulling capacity toward work nobody has committed to. Confirming an order is the moment the plant is told to take it seriously, and it should feel like a decision.

The practical corollary is a maintenance one. Orders that were shipped months ago but never moved past confirmed keep counting as demand, which inflates the projection and pushes replenishment suggestions nobody needs. Closing out is not paperwork; it is what keeps the projected balance honest. Sales orders in EDGEBIC covers the wider model, and what is a sales order status covers the general concept.

The Quote Lifecycle

Quotes carry the longest chain: draft, submitted, under review, approved, rejected, expired, converted.

Most of these are commercial rather than operational: they track where a quotation sits with a customer, which matters to the person chasing it and not at all to the scheduler. Two are different.

Approved means the customer accepted and the quote is ready to become a job. Converted means it has: a real manufacturing order was created from it, carrying the quote's cost fields, markup, unit price, customer link, and scheduling direction forward so the actual run reproduces the quoted plan rather than re-deriving it.

That carry-forward is what makes quoted-versus-actual comparison possible later. The job knows what it was quoted at, so once actuals arrive the variance is a fact rather than an archaeology project. Quote lifecycle from draft to converted covers the sequence, and what is a quote status covers the concept.

Where the Handoffs Are

Read end to end, the three lifecycles form one chain with two doorways.

A quote moves through its commercial stages and, if it is accepted, converts into a manufacturing order. A sales order sits at draft until someone confirms it, and confirmation is what turns it into demand the plan will act on. Everything downstream, the schedule, the projection, the replenishment suggestions, the promise dates, is reading the far side of those two doorways.

That is why status hygiene is a planning activity rather than an administrative one. An unconfirmed order that should have been confirmed is invisible work. A quote left at approved is a job that was never created. Neither shows up as an error, because neither is one.

Where It Fits

Status is how EDGEBIC separates what is real from what is provisional, and what is finished from what is outstanding. Manufacturing orders covers the job record itself, the job status donut covers reading the mix at a glance, the complete EDGEBIC guide maps how the pieces connect, and /edgebic covers the platform as a whole.

The Cheapest Data Quality There Is

Every number a scheduling system produces is filtered by status: which demand counts, which jobs are late, which work is outstanding. That makes status one of the most consequential fields in the database and one of the least maintained, because keeping it current feels like admin and never feels urgent. Confirm the orders that are real, close the ones that shipped, and close out the last operation on a finished job. Three habits, and every downstream number gets more trustworthy without anyone touching a report.