Build a status dictionary
List each status used by the panel and the action it permits. Identify whether it refers to request acceptance, queueing, active delivery, or a final outcome. Ask for clarification where the interface or documentation leaves the state ambiguous.
Separate final from temporary states
A temporary state may still change without a new order. A final state may require support or a separate purchase to proceed. Do not build a workflow that automatically retries every unfamiliar label; first establish whether the original request can still consume funds or deliver.
Preserve original values
When combining reports from several sources, keep both the original label and your internal normalized category. This lets staff investigate an edge case without losing the provider's wording. Update the mapping when documented behavior changes.
Decision checklist
| Decision | What to check |
|---|---|
| Original label | Exact provider wording |
| Meaning | Documented stage |
| Action | Permitted next step |
Worked example
Suppose two hypothetical panels both use processing. One defines it as accepted into a queue, while the other defines it as delivery started. A combined dashboard can group them as active orders but should preserve those distinct meanings.
Example figures explain the decision; they are not current prices or promised results.