لم تتم ترجمة هذه الصفحة بعد — يتم عرض النسخة الإنجليزية.
Numbering sales orders: auto-codes, prefixes and manual codes
Reference guide to sales order numbering systems and how to assign codes.
11 يوليو 2026
Overview
Each sales order is assigned a unique code or number to identify it in reports, invoices, and customer communication. Usystems supports three methods of assigning codes: automatic sequential codes, prefixed codes, and manually entered codes.
Automatic sequential codes
| Feature | Description |
|---|---|
| How it works | Usystems assigns the next number in sequence when you create a sales order. Example: SO-001, SO-002, SO-003. |
| Format | The code typically includes a prefix (set by your business) and an auto-incrementing number. |
| Customization | Your admin can configure the prefix (e.g., "SO" for Sales Order, or a date-based prefix like "2026-07"). |
| Reset options | Some systems reset the counter annually or monthly; ask your admin if resets apply to your business. |
| When to use | Most common for high-volume ordering, especially when customers don't assign their own purchase order numbers. |
Prefixed codes
| Feature | Description |
|---|---|
| How it works | Usystems adds a prefix to the automatic number for additional categorization. Example: SO-REGION-001, SO-REGION-002. |
| Prefix | Usually represents a region, department, product line, or sales channel. |
| Customization | Ask your admin to configure prefixes for your business segments. |
| When to use | Useful for multi-location or multi-department businesses that want to track which region or team created each order. |
Manual codes
| Feature | Description |
|---|---|
| How it works | You enter a custom code directly when creating a sales order. Example: CUSTOMER-001, JAN-2026-50. |
| Format | Any alphanumeric string; follow your company's naming convention for consistency. |
| Flexibility | Useful if your customer has a purchase order number they want to use, or if you follow an external numbering system. |
| Uniqueness | Usystems should prevent duplicate codes; if you try to use the same code twice, the system will warn you. |
| When to use | Used when customers provide their own PO numbers, or when your sales process requires specific numbering patterns. |
Best practices
- Stay consistent: choose one method and stick with it to avoid confusion in reports.
- Communicate with your customer: if they issue purchase order numbers, use those as your sales order codes for easy reconciliation.
- Document your prefix scheme: if using prefixed codes, write down what each prefix means so your team (and auditors) understand the system.
- Check for duplicates: before manually entering a code, verify it does not already exist in the system.
- Include the code in communications: always reference the sales order code in emails, invoices, and delivery notes to the customer.
هل كان هذا مفيدًا؟