For an aluminum saw job queue, ask whether the quoted workflow can set an unfinished order aside at an agreed handoff point, process an urgent order and return to the original remaining quantity. A screen showing stored cut lists does not establish that behavior. The answer must identify what the software retains and what, if anything, people must record separately.
Describe the unfinished-order request
Fictional purchasing case: normal Order A contains a line for 80 pieces. At the proposed business handoff, assume 23 pieces have been recorded complete. Urgent Order B requests 12 pieces. The buyer wants B handled before returning to A’s remaining 57 pieces.
80 − 23 = 57 is invented planning arithmetic. These are not machine readings, customer results or accepted-good-piece counts. “Recorded complete” is the example’s bookkeeping label; its meaning in the actual proposal still needs confirmation. The case assumes no order revision or correction to that starting count.
If the buyer only needs to rearrange waiting orders before production begins, confirm that narrower scope. This case asks something more specific: preserve the progress of an already-started order while another order is handled. “Interrupt” here means that business handoff, not stopping a cutting movement.
Separate saved instructions from the unfinished quantity
For the inquiry, distinguish the reusable instructions for A, the quantity state of its current run, and the choice of which order comes next. A supplier may display these together or use different names. They are purchasing distinctions, not a universal controller layout.
KASTO’s ProControl page, describing controls for its bandsaws, lists saving and reusing orders, cutting plans and office preparation of orders. Those descriptions do not establish that a separate urgent order can interrupt an unfinished batch while preserving its remainder. They are not JiurunCut software specifications.
The RazorGage ST manual’s Android Cutlist Screen section, printed page 33, describes tracking a selected line’s remaining quantity and completing list items out of sequence. That passage concerns selection within a cut list. It does not establish preservation across different order files, shutdown or power loss, or automatic quality acceptance.
Tell the supplier whether A and B are separate orders or files in your proposed workflow. Evidence of changing rows within one list should not silently become proof of retaining A while another order is used.
Put the requested A–B–A handoff beside the offer
Use the same A order reference and line throughout the discussion. Returning to a saved template for a fresh run of 80 pieces is not the requested return to an unfinished balance of 57.
The table describes the buyer’s fictional starting assumption and desired later states. It does not show a successful demonstration, a software algorithm or an operating sequence. Every transition remains for the supplier to explain against the current quotation.
| Business point | Order A record | Order B record | What the supplier must clarify |
|---|---|---|---|
| A before urgent insertion | Assumed start: 80 planned, 23 recorded complete, 57 remaining. | Urgent requirement: 12 pieces; no completion assumed. | What records completion and which business handoff the proposed workflow supports. |
| A held while B is selected | Requested: retain the same A line and its 57-piece balance while its work is deferred. | Requested: B becomes the order to be processed. | Whether A’s state is retained by the quoted function or depends on separately assigned personnel records. |
| Requested return to A after B | Requested: the original A line remains identifiable with 57 still required. | Requested outcome: 12 recorded complete before the return to A; not demonstrated here. | Whether handling the separate order preserves A’s unfinished state, and what work is needed to resume that balance. |
| Requested completion of A’s remainder | Requested: finish the remaining 57, bringing A’s planning count to 80 under the example’s unchanged basis. | B remains a separate order record, not part of A’s count. | How completion of the original A line is identified and any shortfall or replacement requirement is accounted for. |
Ask the supplier to mark each transition as included, dependent on stated manual work, outside the proposal or still unconfirmed. Those replies describe the offered workflow; they do not guarantee that quantities will never be duplicated or missed.
Read the supplier’s reply before accepting the remaining work
Both replies below are fictional. The first says, “Several cut lists can be saved and recalled.” It answers the storage question, but leaves the interrupted A line and its remaining quantity unanswered. Missing evidence is not proof that the machine cannot support the request.
A more specific fictional reply says: “For the configuration and control version identified in our offer, this handoff relies on a separately maintained record of A’s unfinished quantity. Automatic preservation across orders is not included. The responsibility and applicable method for returning to that balance still require confirmation.”
This second reply identifies a personnel-led proposal, not automatic queue handling. The buyer can consider that arrangement once its responsibilities and conditions are clear, or request a proposal that explicitly covers automatic retention if that is essential. More specific wording does not establish better equipment or demonstrate a completed A–B–A run.
If the supplier confirms automatic retention, ask it to identify the covered order/file relationship, control version and return behavior. A software label alone is not the confirmation, and this routine-order question does not establish recovery after a power interruption.
Keep the quantity meaning and physical job conditions visible
Ask what makes the proposed record count a piece as complete. A cycle count or a personnel entry does not, by itself, mean a part has passed inspection. If rework or replacement pieces change the remaining requirement, request the offered workflow’s treatment of that change and who is responsible. Do not silently turn the example’s 23 recorded pieces into 23 accepted pieces.
If A and B use different materials, sections, angles or other requirements, have the supplier identify the conditions for the actual job transition. Retaining business data does not establish that material and equipment are ready for the next task. The inquiry should request that explanation, not prescribe stock changes or machine settings.
A focused purchasing message can read:
Please assess the attached normal-order and urgent-order case for the quoted configuration. Identify the supported handoff point and explain how the original order line and remaining quantity are carried through the urgent job. Distinguish automatic retention from any supplier-defined personnel record or re-entry responsibility, and identify the applicable control version and limits. Define the completion count used, and mark any transition not included or still awaiting confirmation.
If a demonstration is needed, request the supplier’s explanation and evidence for the same unfinished A line before B and upon returning to A, under its approved equipment procedures. A demonstration of a fresh saved job or a different order arrangement does not answer this case. No test is represented as completed here.
- Related file-input scope: Aluminum Cutting List Import: 3 Clear File Checks
- Separate recovery scope: CNC Aluminum Saw Backup: 5 Critical Recovery Questions
Send the two orders and the handoff you need
Share the normal and urgent cut lists, the requested business handoff, the meaning of your quantity record and any manual responsibility you would consider. Mark missing details; incomplete information can start a scope discussion.
Clarify My Urgent-Order and Remaining-Quantity Scope
Ask what the current proposal can support. This article does not establish a JiurunCut job queue, cross-order quantity retention, power-loss recovery or automatic quality-approved counting.