Create a sales order
Learn how to create a sales order in Augno.
To create a sales order in Augno, you need to have created a customer and created a product. Sales orders are created as estimates and then can be: issued to start the fulfillment process, used to generate a production run for the products in the order, and used to generate payment requests for the order. In the current Augno UI flow, the production run is typically created while the order is still in Estimate.
What is a sales order?
A sales order is the order that ties together:
- the customer
- the items/quantities/prices
- the billing & shipping details
- the fulfillment and invoicing workflow
Once created, it becomes the source record for picking, shipping, invoicing, and payment tracking.
Simplest steps
Creating a sales order can be done extremely simply:
Congratulations! You have created a sales order estimate that can now be issued. It can be as simple as that. Because Augno pulls details from the customer, shipping and billing data are pre-filled for you.
Let's also look in more detail at the creation of a sales order.
Required inputs
These are effectively required to create an order.
| Field | What it defines | What it does | Why it’s needed |
|---|---|---|---|
| Customer | Who is buying | Loads customer defaults (addresses, terms, carrier, priority, contacts) | An order must belong to a customer |
| Payment Terms | When/how customer pays | Controls invoice/payment behavior | Needed for billing logic |
| Shipping Terms | Freight responsibility/rules | Affects shipping/freight handling | Needed for fulfillment & freight logic |
| Carrier | Default shipping carrier | Used for shipping rate/line estimation and shipment setup | Needed to plan shipment |
| Priority | Order urgency | Drives operational prioritization | Needed for queueing/ops behavior |
| Bill-to address | Billing destination | Used on invoice and financial docs | Required for valid billing record |
| Ship-to address | Delivery destination | Used for shipment creation/rating | Required for fulfillment |
| At least one line item | What is being sold | Creates order value and fulfillment workload | Without lines there is no order |
Optional inputs
You can leave these blank or set them later.
| Field | What it defines | What it does | Why you’d use it |
|---|---|---|---|
| Customer PO Number | Customer’s internal PO ref | Helps customer-side reconciliation; duplicate warning check runs | Useful for matching your SO to their PO |
| Promised Date | Committed ship/delivery target | Used for scheduling and expectation setting | SLA / commitment tracking |
| Acknowledgement email contacts | Who should get order confirmations | Stores notification recipients for this order | Keep customer contacts informed |
| Invoice email contacts | Who should get invoice notifications | Stores invoice notification recipients | Route invoices to the right people |
| Note | Internal/custom instruction text | Saved on order for ops visibility | Handling instructions, context |
| Manual line price override | Per-line price edit (unlock line) | Lets user override auto-applied price | Exception handling on pricing |
What each section is doing in the create flow
1) Basic details
- Select customer
- Optionally enter customer PO
- Optionally set promised date
- Shows customer type group (read-only context)
What happens behind the scenes: selecting a customer auto-populates terms, addresses, carrier, priority, note, and default notification contacts.
2) Customer-specific order settings
- Payment terms
- Shipping terms
- Carrier & carrier option
- Priority
- Acknowledgement & invoice contacts
- Note
These are the operational defaults for this specific order (even if customer defaults differ later).
3) Addresses
- Bill-to and Ship-to can be edited per order
- Ship-to can be matched to Bill-to quickly
These addresses are saved/linked and used directly for billing and shipment execution.
4) Line items
- Add product & quantity
- Unit price starts from product/customer pricing logic
- Volume discounts/customer prices can auto-apply
- Lock/unlock price per line for manual override
- Order total updates from line values
Auto-generated / system-managed values
You don’t need to enter these manually:
- Sales Order Number: generated by system counter at create time
- Status: starts at initial order status (estimate)
- Created by / ownership links: set from signed-in account/user
- Sales rep assignment: resolved by internal assignment logic
- Shipping line: shipping charge line is generated during create logic
- Change log entry: creation is logged for audit trail
Validation & guardrails you should know
- You cannot create a sales order with zero line items.
- A customer is required before customer-specific terms and contacts can be selected.
- Credit card numbers are blocked in note fields.
- A duplicate customer PO check warns you if the customer PO number is already used for another order.
- If customer is on hold, Augno warns you that issuing the order is blocked until hold is removed.