Appearance
Order Management
Application address: /orders · Product baseline: 0.4.0
Reference status
Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.
Open this screen
Use OSERP navigation to find Order Management, or open /orders on your OSERP application after signing in. Confirm the active company before reading or changing records.
Menu access: orders:read
Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.
Fields and input controls
Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.
Payment method
| Property | Reference |
|---|---|
| Reference key | payment-method |
| Location | Screen / contextual panel |
| Input control | select |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Declared choices: Not set · Cash on delivery · Paid online · Bank transfer · On credit. Choices loaded from records or configuration are not enumerated here.
Courier
| Property | Reference |
|---|---|
| Reference key | courier |
| Location | Screen / contextual panel |
| Input control | EntityPicker |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | Own driver — search to pick a courier |
| Editing | No disabled/read-only condition declared directly on this control. |
Named actions
These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.
- All
- ·
- Advance →
- Scan
- Add photo
Verification still required
Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.
See the operating manual, coverage register, and troubleshooting guide.