Purchase Order
- Code: PUR-PO
- Module: Purchasing
- Type: Transaction
1. Overview
A Purchase Order (PO) is the official document recording a purchase agreement between one store and one supplier, and it is also the starting point of the entire purchasing flow: the PO is the reference for the Goods Receipt (GR) when goods are received, and for the Bill when a bill is created. Every PO has one person in charge (PIC), who is authorized to submit, cancel, and close that order.
Expected outcome: every store has a clear record of its orders, covering what was ordered, from which supplier, and who is responsible, so incoming goods and bills can always be matched against the original agreement.
2. Problem
Without a formal order document, the whole purchasing process depends on informal communication and staff members’ personal notes, from what was ordered and from which supplier, to who approved it. This approach is hard to monitor, error-prone, and leaves no trail that can be traced back. As a result:
- There is no single place to see which orders are running and not yet fulfilled by suppliers per store, so staff have to ask about order status manually.
- It is unclear who is responsible for an order, so it is hard to follow up when mistakes or delays happen.
- Incoming goods are hard to match against the original agreement, so short deliveries or price changes are only discovered when the bill arrives, when it is too late to dispute them.
- Unrecorded purchase commitments leave the owner unable to estimate spending and payment due dates, so cash flow is hard to plan.
3. Goals & Non-goals
3.1 Goals
- Every purchase has a written agreement before goods are shipped, not a verbal agreement that each party only remembers.
- The status of every order is visible in one place, from newly submitted ones to those only waiting for the remaining delivery.
- Responsibility for every order rests with specific people, not with the team in general.
- Quantity or price differences are caught when goods are received, not after the bill is paid.
- The committed purchase value along with its due dates is visible before the bill is issued.
3.2 Non-goals
- Multi-level approval before a PO is submitted; one authorized PIC is enough.
- Sending POs to suppliers directly from the system; POs are downloaded as PDF and sent through each store’s own channels.
- Revising a submitted PO; an incorrect PO is cancelled and created again.
- Copying an old PO into a new one.
- File attachments on POs, even though Goods Receipt and Bill have them.
- Advanced procurement features: requests for quotation (RFQ), price comparison across suppliers, and blanket POs.
- Multi-currency transactions; all values are recorded in a single currency.
4. Business Rules
Business rules are the set of provisions and constraints that apply to POs throughout the application, on every screen and action that involves it, whoever performs it. These rules are the single source of truth: if another part of this PRD appears to differ, the rules here prevail.
- BR-01 Every PO belongs to one store and one supplier. A PO can only be created and edited by users currently working in that store.
- BR-02 Every PO must have a person in charge (PIC) before it can be submitted. Submitting, cancelling, and closing a PO may only be done by a PIC assigned to that PO who has the permission for that action; creating a PO alone does not grant this authority.
- BR-03 The PO’s content, including PIC assignment, can only be changed while it is in Draft status. A submitted PO is permanently locked, and only Draft POs can be deleted.
- BR-04 One product may have more than one discount. Percentage discounts are applied in sequence, each on the remaining value after the previous discount, and only then are nominal discounts subtracted.
- BR-05 Product tax is calculated from the value after discount if it is a percentage, or is a fixed nominal amount.
- BR-06 The due date follows the selected payment term: CBD and COD fall on the estimated received date, EOM at the end of the order date’s month, and Net N falls N days after the order date. Only the Custom term is filled in manually, and filling it in is required.
- BR-07 The estimated received date must not be earlier than the order date.
- BR-08 Each product’s quantity is at least 0.01 and its unit price is at least 1.
- BR-09 A PO can only be cancelled while in Submitted status, and cancellation requires a reason.
- BR-10 Goods receiving progress determines the PO status automatically: partially fulfilled becomes Partially Received, fully fulfilled becomes Received. This status cannot be changed manually.
- BR-11 A PO can only be closed after all of its order has been received.
- BR-12 Goods Receipts and Bills can only be created from POs in Submitted, Partially Received, or Received status.
- BR-13 Every data change and status transition of a PO is recorded along with its actor and time.
5. Flow
5.1 Main Flowchart
- Create PO — Staff prepare the order: the supplier along with its contact, the shipping address, the payment term, and the list of products with their quantity, price, discounts, and tax. All inputs are reviewed before saving.
- Validation — Inputs are checked before the PO is saved. A PO that violates the rules cannot be saved, and the errors are shown in the relevant section.
- Draft — The initial status after the PO is saved. The PO is not yet in effect for the supplier. While in Draft, its content can still be edited and its PIC assigned without changing the status; from here the PO can be submitted or deleted.
- 3a. Edit PO Data — General data and the product list can be updated, and the PO stays in Draft.
- 3b. Assign PIC — One or more store employees are assigned as the person in charge. The PO stays in Draft, and this assignment is required before the PO can be submitted.
- Submitted — Done by the PIC. The PO takes effect, its content is permanently locked, and from this point the PO can be referenced by Goods Receipts and Bills.
- Goods Receipt — Incoming goods are recorded as a receipt referencing this PO. The details are explained in a separate PRD.
- Check Fulfillment — Every time a Goods Receipt is submitted, the quantity received so far is compared with what was ordered to determine the PO’s next status.
- Partially Received — Part of the order has been received and the rest is still awaited. The next receipt is processed as in step 5.
- Received — The entire order has been received. The PO can still be referenced by a Bill for billing.
- Closed — Closed by the PIC after the entire order has been received. The PO cannot be processed further.
- Cancelled — Done by the PIC on a submitted PO that will not proceed, with a required reason.
5.2 Status Lifecycle
| Status | Description | Next |
|---|---|---|
Draftdraft | Being prepared, not yet in effect for the supplier | Submitted, or deleted |
Submittedsubmitted | In effect and locked, waiting for goods to arrive | Partially Received, Received, Cancelled |
Partially Receivedpartially_received | Part of the order has been received, the rest is still awaited | Received |
Receivedreceived | The entire order has been received | Closed |
Closedclosed | Closed by the PIC, not processed further | — |
Cancelledcancelled | Cancelled before any receipt | — |
6. Document Structure
This section defines the content of the PO document itself: which fields a PO has, their type, which are required, their initial values, their value rules, and their calculation formulas. The provisions here apply wherever the PO is created or changed and are enforced on save, regardless of how the field is displayed.
6.1 General
| Field | Type | Required | Default | Rules |
|---|---|---|---|---|
| PO Number | Text | — | Generated on save | Set by the system in the format PO/{Store Code}/{Year}/{000000}, cannot be changed |
| Store | Ref. Store | Yes | The store where the user is currently working | Cannot be changed (BR-01) |
| Supplier | Ref. Supplier | Yes | — | Selected from the Supplier master (BR-01) |
| Contact | Ref. Supplier Contact | Yes | — | Belongs to the selected supplier |
| Shipping Address | Ref. Store Address | Yes | The store’s default shipping address, or its first address | Belongs to the store |
| Order Date | Date | Yes | Today | — |
| Estimated Received Date | Date | Yes | — | Must not be earlier than the Order Date (BR-07) |
| Payment Term | Enum | Yes | — | CBD, COD, EOM, Net 14, Net 30, Net 60, Net 90, or Custom |
| Due Date | Date | Yes, if the term is Custom | Calculated from the Payment Term | Only filled in manually for the Custom term (BR-06) |
| Person in Charge (PIC) | Ref. Employee, multiple | Yes, before submitting | — | Store employees; can only be filled in by holders of the assign permission (BR-02) |
| Notes | Text | No | — | — |
| Status | Enum | — | Draft | Set by the system; see Status Lifecycle |
6.2 Line Items
| Field | Type | Required | Default | Rules |
|---|---|---|---|---|
| Sequence | Integer | — | Follows the order of addition | Set by the system |
| Product (Package) | Ref. Store Product Inventory | Yes | — | One row per package |
| Measurement Unit | Text | — | Follows the selected package | Set by the system |
| Quantity | Decimal | Yes | 1 | At least 0.01 (BR-08) |
| Unit Price | Currency | Yes | The package’s cost | At least 1 (BR-08) |
| Percentage Discount | Percent, multiple | No | — | Applied in sequence according to their order (BR-04); a value of 0 is not saved |
| Nominal Discount | Currency, multiple | No | — | Subtracted after the Percentage Discounts (BR-04); a value of 0 is not saved |
| Tax | Percent or Currency | No | Percent, 0 | Calculated from the value after discount (BR-05) |
6.3 Calculations
| Field | Formula |
|---|---|
| Total Gross Price | Sum of (Quantity × Unit Price) across all lines |
| Total Discount | Sum of discounts across all lines, applied in sequence per line (BR-04) |
| Total Net Price | Total Gross Price − Total Discount |
| Total Tax | Sum of tax across all lines, calculated from the value after discount (BR-05) |
| Grand Total Price | Total Net Price + Total Tax |
7. UI Structure
This section defines how POs are displayed and operated: the list columns, filters, form controls along with their option sources, and the PDF layout. This section only governs display and interaction; content and value rules still follow Document Structure.
7.1 Datatable
| Column | Sortable | Sample Value | Component |
|---|---|---|---|
| Select | — | — | Checkbox, Expand Toggle |
| No | — | 1 | Number |
| PO Number | Yes | PO/CBI/2026/000042 | Link |
| Store | — | Cianjur Store | Text |
| Order Date | Yes | 23 Sep 2026 | Date |
| Estimated Received Date | Yes | 30 Sep 2026 | Date |
| Due Date | Yes | 23 Oct 2026 | Date |
| Person in Charge | — | Andi, Sari | Accordion, Add Button |
| Supplier | — | PT Sumber Rejeki | Text |
| Total Gross Price | — | Rp 12,500,000 | Currency |
| Total Discount | — | Rp 500,000 | Currency |
| Total Net Price | — | Rp 12,000,000 | Currency |
| Total Tax | — | Rp 1,320,000 | Currency |
| Grand Total Price | Yes | Rp 13,320,000 | Currency |
| Created By | — | Budi Santoso | Text |
| Status | — | Submitted | Badge |
| Actions | — | Print · View · Edit · Delete | Action Menu |
Expanded Row
| Column | Sample Value | Component |
|---|---|---|
| Product (Package) | Cooking Oil 2L (Carton) | Thumbnail, Text |
| Quantity | 10 | Number |
| Measurement Unit | Carton | Text |
| Unit Price | Rp 250,000 | Currency |
| Gross Price | Rp 2,500,000 | Currency |
| Discount | Rp 250,000 | Currency |
| Net Price | Rp 2,250,000 | Currency |
| Tax | Rp 247,500 | Currency |
| Total Price | Rp 2,497,500 | Currency |
7.2 Advance Filter
| Field | Control | Options Source | Default |
|---|---|---|---|
| Store | Multi Select | Stores assigned to the user | Empty |
| Order Date Range | Date Range Picker | — | Empty |
| Supplier | Multi Select | Supplier master, searchable | Empty |
| Status | Multi Select | Status enum | Empty |
7.3 Form & Details
Create — A three-step wizard: General, Products, then Review. The Next button validates the current step before moving on, and the Review step shows a read-only summary of all inputs. Actions: Next, Save, PDF Preview.
Edit — Two tabs, General and Products, with all fields enabled. Only available while the PO is in Draft. Actions: Save, add/edit/delete product, PDF Preview.
Detail — The PO number, status badge, and status stepper at the top, followed by read-only General and Products tabs. Actions: Edit Data, Submit, Cancel, Close, Print, and Activity Logs, each appearing according to the PO status. Status action buttons are still shown to users who are not the PIC, but in a disabled state.
General
| Field | Control | Options Source | Behavior |
|---|---|---|---|
| Store | Read-only | The store where the user is currently working | — |
| Shipping Address | Single Select | The store’s addresses | — |
| Order Date | Date Picker | — | Changed → Due Date is recalculated |
| Estimated Received Date | Date Picker | — | Dates before the Order Date cannot be selected |
| Person in Charge (PIC) | Multi Select | Store employees | Can only be filled in by holders of the assign permission |
| Supplier | Single Select | Supplier master, searchable | Changed → Contact is cleared |
| Contact | Single Select | Contacts of the selected supplier | Disabled until a Supplier is selected |
| Payment Term | Single Select | Payment term enum | Changed → Due Date is recalculated |
| Due Date | Date Picker | — | Disabled except for the Custom term |
| Notes | Textarea | — | — |
Products — Table
| Column | Sample Value | Component |
|---|---|---|
| Product (Package) | Cooking Oil 2L (Carton) | Thumbnail, Text |
| Quantity | 10 | Number |
| Measurement Unit | Carton | Text |
| Unit Price | Rp 250,000 | Currency |
| Gross Price | Rp 2,500,000 | Currency |
| Discount | Rp 250,000 | Currency |
| Net Price | Rp 2,250,000 | Currency |
| Tax | Rp 247,500 | Currency |
| Total Price | Rp 2,497,500 | Currency |
| Actions | Edit, Delete, View | Action Menu |
Products — Form
| Field | Control | Options Source | Behavior |
|---|---|---|---|
| Product (Package) | Single Select | Store product inventory, one option per package, searched by name or barcode | Fills in Measurement Unit and Unit Price |
| Measurement Unit | Read-only | The selected package | — |
| Quantity | Number Input | — | — |
| Unit Price | Currency Input | — | The last purchase price is shown as a reference next to the label |
| Percentage Discount | Percent Input, can be more than one | — | The row order determines the calculation order |
| Nominal Discount | Currency Input, can be more than one | — | — |
| Tax | Number Input with a percent or nominal option | — | — |
Products — Calculations
| Field | Sample Value | Component |
|---|---|---|
| Total Gross Price | Rp 12,500,000 | Currency, read-only |
| Total Discount | Rp 500,000 | Currency, read-only |
| Total Net Price | Rp 12,000,000 | Currency, read-only |
| Total Tax | Rp 1,320,000 | Currency, read-only |
| Grand Total Price | Rp 13,320,000 | Currency, read-only |
7.4 PDF Format
| Section | Content |
|---|---|
| Watermark | The PO status, only on Draft and Cancelled POs |
| Header | - Company: Name, Contact, Address - Document: Purchase Order title, PO Number, Order Date |
| Parties | - Supplier: Name, Address - Contact: Name, Phone - Ship To: Store Name, Shipping Address |
| Product Table | No | Product | Quantity | Measurement Unit | Unit Price | Gross Price | Discount | Net Price | Tax | Total Price |
| Summary | - Details: Estimated Received Date, Payment Term, Due Date - Notes: Content of the Notes field - Calculations: Total Gross Price, Total Discount, Total Net Price, Total Tax, Grand Total Price |
| Signature | Person in Charge column along with their names, only on POs that have left Draft status |
8. User Stories
US-01 - Create a PO
As purchasing staff, I want to create a PO containing the supplier, shipping address, terms, and product list, so that the order is recorded before the goods arrive.
| ID | Acceptance criteria |
|---|---|
| AC-01.1 | When a user with the create permission opens Add New in the active store, the General → Products → Review wizard appears with the active store filled in (read-only) and today’s order date. |
| AC-01.2 | The shipping address is filled in automatically with the store’s default shipping address; if there is none, the store’s first address. |
| AC-01.3 | When the supplier is changed, the contact is cleared and the contact options are taken from the selected supplier’s contacts. Contact is disabled until a supplier is selected. |
| AC-01.4 | When the payment term, order date, or estimated date changes, the due date is recalculated according to BR-06. For the Custom term, the due date must be filled in manually. |
| AC-01.5 | The estimated received date cannot be selected before the order date (BR-07). |
| AC-01.6 | The product dialog provides search by name or barcode, with each product package as a separate option. When a product is selected, the measurement unit is filled from the selected package, the default price from the package’s cost, and the last purchase price is shown as a reference. |
| AC-01.7 | When the quantity, price, discount, or tax changes, the product total and grand total are updated without reloading, calculated according to BR-04 and BR-05. |
| AC-01.8 | When Next is clicked and required fields in that step are empty, the user cannot move to the next step and errors appear on the related fields. |
| AC-01.9 | When Save succeeds, the PO is saved in Draft status, a success toast appears, and the user is redirected to the PO list. |
| AC-01.10 | When saving is rejected, error messages appear in the Review step and on the related fields. |
| AC-01.11 | When the user leaves the wizard with unsaved input, an unsaved changes confirmation appears. |
| AC-01.12 | The active store is inactive — the Add page shows the inactive store page. |
| AC-01.13 | The user is not assigned to any store — the PO page shows the no store assigned page. |
| AC-01.14 | The order date is changed to after the estimated date — the estimated date picker only restricts new selections; data that violates BR-07 is rejected on save. |
| AC-01.15 | The payment term is changed from Custom to another term — the due date is recalculated automatically and the field becomes disabled (BR-06). |
| AC-01.16 | The same product with a different package — allowed; each package is recorded as a separate line. |
US-02 - Edit a Draft PO
As purchasing staff, I want to edit a PO that is still in Draft, so that mistakes can be fixed before it is submitted.
| ID | Acceptance criteria |
|---|---|
| AC-02.1 | The Edit Data button only appears on Draft POs for users with the update permission in the active store (BR-03). |
| AC-02.2 | The General tab is saved as a whole; products in the Products tab are added, edited, and deleted one at a time and saved immediately. |
| AC-02.3 | When the edit URL is opened on a PO that is not in Draft, the page returns to the read-only detail view (BR-03). |
| AC-02.4 | The open tab stays the same when switching from detail to edit. |
US-03 - Assign the person in charge
As a store manager, I want to assign a PIC on a PO, so that it is clear who is authorized to submit, cancel, and close the PO.
| ID | Acceptance criteria |
|---|---|
| AC-03.1 | More than one PIC can be selected from the store’s employee list, when creating a PO, when editing a Draft, or through the add button in the Person in Charge column of the list (BR-03). |
| AC-03.2 | The add PIC button in the list only appears on Draft POs for users with the assign permission in the active store (BR-03). |
US-04 - Submit a PO
As a PIC, I want to submit a PO, so that the PO takes effect and its content no longer changes.
| ID | Acceptance criteria |
|---|---|
| AC-04.1 | The Submit Order button appears on Draft POs for users with the submit permission, and is only enabled if the user is that PO’s PIC (BR-02). |
| AC-04.2 | After confirmation, the status becomes Submitted, and who submitted it and when are recorded. |
| AC-04.3 | On a Submitted PO, the Edit Data button and product actions do not appear (BR-03). |
| AC-04.4 | The PO has no PIC yet — the Submit button is disabled for all users until a PIC is assigned (BR-02). |
| AC-04.5 | A user who is not the PIC opens the PO — the Submit, Cancel, and Close buttons appear but are disabled (BR-02). |
US-05 - Cancel a PO
As a PIC, I want to cancel a PO that will not go ahead, so that it is not treated as an order being awaited.
| ID | Acceptance criteria |
|---|---|
| AC-05.1 | The Cancel Order button appears on Submitted POs for users with the cancel permission, and is only enabled if the user is the PIC (BR-02, BR-09). |
| AC-05.2 | The cancellation dialog requires a reason; the confirm button is disabled while the reason is empty (BR-09). |
| AC-05.3 | After cancelling, the status becomes Cancelled; the reason, who, and when are saved. The status stepper shows the path Draft → Submitted → Cancelled. |
US-06 - View receiving progress
As purchasing staff, I want the PO status to change according to goods receiving, so that I know what is still awaited.
| ID | Acceptance criteria |
|---|---|
| AC-06.1 | When a GR referencing the PO is submitted for part of the quantity, the PO status becomes Partially Received (BR-10). |
| AC-06.2 | When all products are fulfilled, the PO status becomes Received (BR-10). |
| AC-06.3 | The ordered, received, and remaining quantity per product appear in the Purchase Items module, and can be filtered per PO. |
| AC-06.4 | The supplier will not deliver the remaining goods (PO Partially Received) — there is no action yet; the PO stays Partially Received because Close is only from Received (BR-11) and Cancel is only from Submitted (BR-09). |
| AC-06.5 | Goods received exceed the ordered quantity — allowed through a GR; the product is marked over-received in the Purchase Items module (the tolerance is governed in the Goods Receipt PRD). |
US-07 - Close a PO
As a PIC, I want to close a PO that has been fully received, so that the PO is marked as finished.
| ID | Acceptance criteria |
|---|---|
| AC-07.1 | The Close Order button appears on Received POs for users with the close permission, and is only enabled if the user is the PIC (BR-02, BR-11). |
| AC-07.2 | After confirmation, the status becomes Closed, and who closed it and when are recorded. |
US-08 - PO list and search
As an owner, I want to view and filter POs, so that I can quickly find orders that have not arrived yet.
| ID | Acceptance criteria |
|---|---|
| AC-08.1 | By default, the active store’s POs are shown; advanced filters: store, supplier, date range, and status; keyword search. |
| AC-08.2 | Columns: number, store, order date, estimated received date, due date, person in charge, supplier, total gross price, total discount, total net price, total tax, grand total price, created by, and status. |
| AC-08.3 | Default sort by latest order date at the top, with pagination. Sortable columns: order date, number, estimated received date, due date, and grand total price. |
| AC-08.4 | Rows can be expanded to see the PO’s product list without opening the detail. |
| AC-08.5 | Row actions: Print, View, Edit (Draft only), Delete (Draft only), according to permissions (BR-03). |
US-09 - Delete a Draft PO
As purchasing staff, I want to delete Drafts that will not be used, so that the list stays clean.
| ID | Acceptance criteria |
|---|---|
| AC-09.1 | The Delete action is only available on Draft POs for users with the delete permission in the active store, after confirmation (BR-03). |
| AC-09.2 | Bulk delete is available from the selected rows in the list. |
US-10 - Print a PO
As purchasing staff, I want to print or download a PO as a PDF, so that it can be sent to the supplier.
| ID | Acceptance criteria |
|---|---|
| AC-10.1 | PDF preview is available from the create PO wizard, the detail/edit page, and the Print action in the list, in any status. |
| AC-10.2 | When editing a Draft, the PDF preview uses the latest unsaved form input. |
| AC-10.3 | Before the PO is saved, the PO number on the PDF is shown empty (”-”). |
| AC-10.4 | The PDF contains the PO notes. |
US-11 - Activity history
As an owner, I want to see the PO activity log, so that I know who changed what and when.
| ID | Acceptance criteria |
|---|---|
| AC-11.1 | The activity log is available per PO (in the detail) and for all POs (in the list) (BR-13). |
9. User Scenarios
| Role | Scenario |
|---|---|
| Purchasing Staff | Creates a weekly restock PO to one supplier for their store, assigns a PIC (themselves or another staff member), then submits it and prints the PDF to send via WhatsApp |
| Purchasing Staff | The PO is submitted to the supplier, goods arrive partially and are recorded through Goods Receipt, the rest follows the next week, then a Bill is created from the total received and paid in installments until fully paid |
| Owner | Views all POs across stores, filters them by status and supplier, and monitors payment due dates |
10. Permissions & Actions
10.1 Permission by Action
| Action | Permission | Condition |
|---|---|---|
| View PO List (All Stores) | purchase:purchase-order:list:any | — |
| View PO List (Assigned Stores) | purchase:purchase-order:list:store | — |
| View PO Detail (All Stores) | purchase:purchase-order:view:any | — |
| View PO Detail (Assigned Stores) | purchase:purchase-order:view:store | — |
| Create PO | purchase:purchase-order:create:store | Store is active |
| Edit PO (General Data) | purchase:purchase-order:update:store | Store is active |
| Delete PO | purchase:purchase-order:delete:store | Store is active |
| View Product Detail | — | Follows the view PO detail permission |
| Add Product | purchase:purchase-order:update:storepurchase:purchase-order:create:store | Store is active |
| Edit Product | purchase:purchase-order:update:store | Store is active |
| Delete Product | purchase:purchase-order:update:storepurchase:purchase-order:delete:store | Store is active |
| Assign PIC | purchase:purchase-order:assign:store | Store is active, from the PO list |
| Submit | purchase:purchase-order:submit:store | Store is active, user is the PIC |
| Cancel | purchase:purchase-order:cancel:store | Store is active, user is the PIC |
| Close | purchase:purchase-order:close:store | Store is active, user is the PIC |
10.2 Action by Status
| Action | Draft | Submitted | Partially Received | Received | Closed | Cancelled |
|---|---|---|---|---|---|---|
| Edit PO (General Data) | ✓ | — | — | — | — | — |
| Delete PO | ✓ | — | — | — | — | — |
| View Product Detail | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Add Product | ✓ | — | — | — | — | — |
| Edit Product | ✓ | — | — | — | — | — |
| Delete Product | ✓ | — | — | — | — | — |
| Assign PIC | ✓ | — | — | — | — | — |
| Submit | ✓ | — | — | — | — | — |
| Cancel | — | ✓ | — | — | — | — |
| Close | — | — | — | ✓ | — | — |
| Referenced by GR and Bill | — | ✓ | ✓ | ✓ | — | — |
| Preview and Print PDF | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| View Activity Logs | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
11. Notifications
This feature does not trigger any notifications.
12. Dependencies
Related PRDs
- Goods Receipt — receiving goods from a PO, which changes the PO status (BR-10), and the over-receive tolerance (see US-06).
- Bill — bills referencing the PO and GR (BR-12).
- Purchase Order Line — view of the ordered, received, and remaining quantity per PO item (AC-06.3).
Master data
- Stores — the active store, active status, shipping address, and employees (PIC).
- Suppliers — supplier data and its contacts.
- Products & Product Inventory — packages/measurement units, barcodes, cost, and last purchase price per store.
Effects on other modules
- A PO does not change stock; stock increases when a GR is submitted.
- POs that are Submitted, Partially Received, or Received appear as options on the Goods Receipt and Bill forms.
- Every change is recorded in the activity log (BR-13).