How to Run the Sales Order Progress Report in EDGEBIC

The sales order progress report in EDGEBIC by User Solutions lives in the Reports hub: it returns every job grouped by sales order and customer, each with its percent complete, planned and actual hours, and how many days its scheduled end lands ahead of or behind the due date. It is the report that turns a pile of jobs into a per-customer fulfillment view.

Where job progress answers "how far along is this job", sales order progress answers "how far along is this customer's whole order". It pairs naturally with on-time delivery for the outward-facing picture, and how the report family divides up is in EDGEBIC reports explained. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Jobs are linked to sales orders. The grouping is by sales order, so unlinked jobs fall into an unassigned bucket.
• Jobs are scheduled. Planned hours and the days-versus-due signal both come from the schedule.
• Actual hours are being logged if you want percent complete to reflect reality.

Step 1: Open the Report

Open Reports from the main navigation and click the Sales Order Progress card. Launched from the hub, the report loads every sales order with no date prompt. The grid arrives grouped by sales order reference and then by job number, sorted so orders read in reference order.

Step 2: Read a Job Row

Each row is one job inside a sales order group:

• Percent complete, actual hours over planned hours, capped at 100.
• Planned, actual, and remaining hours, so you can see the size of the job and what is left.
• Scheduled start and end, the planned window.
• Days versus due, positive when the scheduled end lands after the due date, negative when it lands early.
• Status, the job's current state.
• Customer, carried from the sales order.

Step 3: Read a Whole Order at Once

Because the grid is grouped by sales order, a customer's jobs already sit together under one header. Read across the group and you have the order's status in one view: which jobs are complete, which are on track, and which are running late. This is the fastest way to answer a customer asking about their entire order rather than one line of it.

Step 4: Isolate One Order to Export

To send a clean status for a single order, right-click the sales order reference column header, choose Filter Editor, and set the filter to that reference or that customer name. The grid narrows to the group. Click Export in the toolbar and save it. The exported group is a per-order status ready to hand over, without assembling it from separate lookups.

How to Check It Worked

The report is a read-only snapshot, so nothing is saved. Confirm it worked by checking that a job you know is finished reads near 100 percent complete and that its days-versus-due figure matches what you expect. If jobs you believe are nearly done read low, the usual cause is that actual hours are not being logged; confirm on the Daily Production report.

Common Mistakes

• Ignoring the unassigned group. Jobs not linked to a sales order pool into an unassigned bucket. If a customer's job is missing from their group, check whether it is unlinked.
• Reading percent complete without checking actuals. It is actual hours over planned hours, so an unlogged shop reads low regardless of physical progress.
• Confusing days-versus-due with percent complete. One measures the date landing, the other measures logged effort. A job can be late and nearly complete, or early and barely started.
• Forgetting the parallel-hours setting. For jobs that fan out across parallel stations, the primary-hours-only setting governs how the job total rolls up so mirror hours are not double counted.

Related Reading

• On-time delivery report: the trend view of whether orders land on time.
• How to simulate a delivery date for a quote: promise dates before the order exists.
• EDGEBIC platform overview: where order tracking fits in the wider system.