Purchase
Sort Purchases by Date, Amount, Delivery or Supplier
Sort changes the order of the merged purchase working list. Choose the question first, apply one sort, and verify the first rows before acting or exporting.
- Menu path
- Purchase -> Purchases -> Sort
- Verified from
- Posnic demo and current POS source reviewed on 2026-09-08
Technical source evidence
frontend/static/script/js/modules/js/receiving_add.js purchaseorders.loadList CMP, frontend/static/script/js/core/PosnicPro.js listSort mount value, purchase PAGE_SIZE 25 fetchLimit 100 per source when sorted, client-side merged purchase-order and receiving sort
Sort a Purchase List
- Open Purchase -> Purchases and wait for the list and count to finish loading.
- Apply any Search, date, Status or Expected controls needed for the task.
- Click Sort in the top action row.
- Choose one sort option from the menu.
- Wait for the list to reload and return to page 1.
- Check the Sort button label and inspect the first several rows.
- Open the purchase you intend to receive, return, print, email or review.
- Choose Default when the special ordering is no longer needed.
What Each Sort Option Means
| Option | Rows placed first | Use it for |
|---|---|---|
| Default | Newest Bill date first; equal Bill dates use newest Created first. | Recent purchasing and receiving activity. |
| Bill date: oldest | Oldest Bill date first; equal Bill dates use oldest Created first. | Finding aged documents in the loaded list. |
| Highest amount first | Largest numeric Total first. | Reviewing high-value purchases and approval checks. |
| Lowest amount first | Smallest numeric Total first. | Finding low-value entries or possible test documents. |
| Expected: soonest | Earliest valid Expected date first. | Following deliveries due soon. |
| Supplier A to Z | Supplier names in browser locale alphabetical order. | Reviewing adjacent records from similarly named suppliers. |
Understand the Sorting Scope
The Purchases screen combines two sources: purchase orders and received purchases. When a special sort is active, the browser requests up to 100 records from each source, merges them, applies the chosen comparison and then displays 25 rows per page.
- Sort is applied to the loaded merged working window, not unlimited purchase history.
- A shop with more than 100 orders or more than 100 received purchases may have older matching records outside the sorted window.
- Changing the sort reloads page 1.
- The same sorted row order is used by Export CSV for the rows currently loaded.
- Use Purchase Reports when a complete date-controlled register is required.
Expected Date Rules
Expected: soonest compares real expected-delivery timestamps. A row without an Expected date is placed after rows that have one.
- Use this sort to prioritize supplier follow-up, not to prove stock is late.
- Check Status because a Received row can still carry historical expected-date information.
- Use the Expected quick filter for today, tomorrow or this week when the visible list must be narrowed.
- Open the row and compare the expected date with supplier communication before escalating.
- Missing Expected dates should be corrected in the source order when delivery planning depends on them.
Amount and Supplier Review
| Question | Recommended sort | Verification |
|---|---|---|
| Which loaded purchase has the greatest total? | Highest amount first | Open the first row and verify charges, tax and invoice total. |
| Are there unusually small entries? | Lowest amount first | Check whether they are valid small purchases, drafts or test data. |
| Which supplier records sit together? | Supplier A to Z | Check supplier identity; similar names can still be separate supplier records. |
| What is oldest in the working list? | Bill date: oldest | Compare Bill date with Created and Status before deciding it is overdue. |
| What happened most recently? | Default | Remember Default prioritizes Bill date, then Created time for ties. |
Sort, Filter and Export Are Different
Sort controls order, filters control which rows are shown, and Export CSV writes the loaded row set. These controls are related but they are not interchangeable.
- A sorted list is not automatically a filtered list.
- Status and Expected quick filters can narrow the visible rows without narrowing the current CSV export.
- Search and date filters target received-purchase requests while purchase orders are loaded separately.
- After changing any control, verify the first and last relevant purchase numbers before acting.
- Do not use the first row alone as proof of a full-history maximum, minimum or oldest purchase.
Sorting Problems and Corrections
| Problem | Likely reason | Correction |
|---|---|---|
| Newest purchases are no longer first | A special sort remains selected. | Open Sort and choose Default. |
| Oldest result is not the oldest in shop history | Sorting covers the loaded working window. | Use a Purchase Report with the required date range. |
| Expected sort puts some rows at the bottom | Those rows have no valid Expected date. | Open the purchase order and verify or add its expected date. |
| Two same-date rows look unexpectedly ordered | Bill date ties are resolved using Created time. | Compare both Bill date and Created columns. |
| Supplier order looks different from a strict code list | Names use browser locale comparison. | Normalize supplier names and remove accidental prefixes or spacing. |
| Export order changed | The CSV follows the current loaded sort order. | Choose the required sort before export and label the resulting file. |
| Sort label changed but rows are still loading | The list reload has not completed. | Wait for rows and purchase count before selecting a document. |