> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # CloudHub Purchase Orders, Suppliers, Goods Received, Accounts Payable > How to run the buying loop in 247CloudHub Locate. Create POs, manage suppliers, receive goods, and track payable invoices end to end for multichannel ecommerce. These four pages run the buying loop inside 247CloudHub Locate: identify the supplier, raise the PO, receive the goods, pay the invoice. They are the upstream half of the operational chain. Each page links to the others so a buyer can move through the loop without leaving the surface. ## Suppliers Management Path: Home, Locate, Suppliers. Suppliers Management is the supplier master record. Every PO must reference a supplier from this list. The grid columns are: | Column | What it means | | ---------------------------------------------------- | ----------------------------------------------------------------- | | Action | Edit per row | | Supplier ID | Internal supplier ID | | Supplier Name | Trading name of the supplier | | Contact Name, Contact Phone Number, Contact Email ID | Primary contact details | | Product Count | Number of distinct SKUs sourced from this supplier | | Payment Terms | Standard payment terms (e.g. Net 30, Net 60) | | Last Invoice Raised on, Last PO Raised on | Most recent activity dates | | Last PO Status | The state of the most recent PO (Pending, Acknowledged, Received) | | Next Delivery Date | Expected next inbound delivery | | Credit Limit | Approved spend ceiling per period | | Invoices to Pay, Invoices Paid | Counts feeding the AP page | | Status | Active or Blocked | Top-bar actions: `Add Supplier`, `Delete Supplier`, `Block Supplier`, `Unblock Supplier`, `Export Supplier`. Use cases: 1. **New supplier onboarding.** Create the supplier record before raising the first PO. Get the contact, terms, and credit limit right at the start; you will reference them on every future PO. 2. **Supplier audit.** Sort by `Last PO Raised on` ascending to see suppliers you have not bought from in months. Either re-engage or remove them. 3. **Block a supplier without losing history.** Use `Block Supplier` rather than `Delete Supplier` when a supplier is paused. Blocking keeps the historical PO and AP records intact while preventing new POs. Common gotcha: deleting a supplier with historical POs orphans the PO records' supplier reference. Use Block instead of Delete unless you genuinely want the supplier wiped from the system. ## Purchase Orders Path: Home, Locate, Purchase Orders. The PO grid lists every open and recent PO. Top-bar actions: `Create Purchase Order`, `Send Purchase Order`, `Delete Purchase Order`, `Manage Goods Received`, `Manage Suppliers`, `Manage Bin Locations`, `Manage Warehouses`. The status callouts top-right show running counts: `Awaiting PO`, `Backordered`, `Delivered`. Each PO row shows: | Column | What it means | | ---------------------- | ------------------------------------------------------------------------- | | Action | Edit | | PO No | Internal PO number | | Supplier Name | The supplier this PO is raised against | | Expected Delivery Date | When the supplier committed to deliver | | No. of Products | Distinct SKUs on this PO | | PO Raised On | Creation date | | Payment Terms | The payment-terms string from the supplier record (or override on the PO) | | Currency | Currency the PO is denominated in (GBP, USD, EUR) | | Deliver To | Target warehouse (when multi-warehouse is enabled) | The PO lifecycle: 1. **Create.** Click `Create Purchase Order`, pick the supplier, add SKU lines with quantity and unit cost. Save. 2. **Send.** Click `Send Purchase Order` against the new PO. CloudHub emails the formatted PO to the supplier's contact email. 3. **Acknowledge.** When the supplier confirms, the PO status moves to Acknowledged. (Some workflows mark this manually; some integrate via supplier portals.) 4. **Goods Received.** When the inbound delivery arrives, mark goods received via the Goods Received page below. 5. **Invoice match.** When the supplier invoice arrives, match it to the PO and record payment via Accounts Payable. Use cases: 1. **Daily PO triage.** Filter to POs older than their `Expected Delivery Date` with status not Delivered. That is the chase list. 2. **Multi-warehouse stock-routing.** Set `Deliver To` per PO so inbound goods land at the right warehouse for the demand pattern. 3. **Currency awareness.** International POs in non-base currency need to be margin-checked against the current FX rate before the goods land. Common gotcha: editing a PO after `Send Purchase Order` requires you to resend it. The supplier sees only what was last emailed. Always re-send when quantities or prices change. ## Goods Received Path: Home, Locate, Goods Received. This page lists every goods receipt against an open PO. | Column | What it means | | --------------------------- | ---------------------------------------------------------------- | | Action | Edit per row | | GRN No | Goods Received Note number, internal | | PO No | The PO this receipt is against | | Goods Received On | Date the goods arrived | | No. of Products Ordered | Quantity on the PO | | No. of Products Received | Actual quantity unloaded | | No. of Products Backordered | Difference (ordered minus received) | | No. of Products Damaged | Damaged on arrival | | Deliver To | Target warehouse | | Bin Location | Final put-away bin (auto-populated when bin scanning is enabled) | | Created By | The user who recorded the receipt | Top-bar action: `Accept Goods Received` triggers the receipt workflow. Use cases: 1. **Partial receipt.** When the supplier ships fewer units than ordered, record the actual count. The PO stays open with `Backordered` count for the shortfall, and the next inbound from that supplier closes it. 2. **Damage flagging.** Mark damaged units in `No. of Products Damaged` so the credit-note conversation with the supplier has a CloudHub-side record. 3. **Stock placement.** When bin-scanning is enabled, `Bin Location` is captured at putaway, which feeds the [Warehouse and Stock Locations](/vortex-apps/cloudhub/locate-warehouse/stock-locations) view. Common gotcha: if you forget to accept goods received, the [Products report](/vortex-apps/cloudhub/analyse-reports/inventory-and-products#products-report) will show `Awaiting PO` quantity as still outstanding even though the goods are physically on shelves. Always accept the GRN at putaway. ## Accounts Payable Path: Home, Locate, Accounts Payable. The AP page lists every supplier invoice raised against a PO and tracks payment status. | Column | What it means | | ----------------------- | ------------------------------------- | | Action | Record Payment | | PO No | The PO the invoice is against | | Supplier Invoice number | The supplier's invoice reference | | PO Status | Pending, Partially Received, Received | | PO Total Amount | The full PO value | | PO Backordered Amount | The unreceived value | | Amount to be paid | The current outstanding | | Payment Due Date | When the invoice is due | | Payment Status | Paid, Pending, Overdue | | Last Payment Paid on | When the most recent payment posted | | Supplier Name | The supplier on the invoice | Top-bar action: `Record Payment` on a row opens the payment dialog. Record amount paid, payment date, and reference. Use cases: 1. **Cash-flow forecast.** Filter by `Payment Due Date` to see what is due this week, next week, and next month. That is the upcoming cash outflow. 2. **Overdue chase.** Filter to `Payment Status = Overdue`. That is the supplier-relationship-protection list. 3. **Reconcile to ERP.** Export AP and reconcile against the supplier statement and the GL accruals. The Vortex IQ AP module is operational; the ERP remains the financial source of truth, but the operational view is what signals problems early. Common gotcha: the `Amount to be paid` column reflects the outstanding net of payments recorded in CloudHub. If you pay a supplier outside the system and forget to record the payment here, AP will misrepresent the outstanding. Either record every payment in CloudHub, or reconcile from your bank statement before treating AP as authoritative. ## How the four pages connect The buying loop runs in this order: 1. **Suppliers** master record (set up once per supplier). 2. **Purchase Orders** raised against the supplier. 3. **Goods Received** when inbound arrives. 4. **Accounts Payable** when the invoice arrives. Quick links across the top of Purchase Orders and Goods Received cross-link the four pages in one click. The status counters at the top of Purchase Orders (`Awaiting PO`, `Backordered`, `Delivered`) are the rolling KPI for the loop. ## Cross-link to the rest of the AI OS | Need | Where to go | | ------------------------------------------------------------------- | ----------------------------------------------- | | Live inventory KPI | Nerve Centre, the connector card | | "Which suppliers are slipping on lead time?" | Vortex Mind, supplier-performance investigation | | "What is the total value of POs in flight to Supplier 9 right now?" | Ask Viq, plain-English query | | "Open a fix for the late supplier 7 delivery" | Actions Kanban | ## Common questions **Can I attach the supplier-issued invoice PDF to a PO?** PDF attachment is in roadmap; today, the supplier invoice number and the financial fields are captured on the AP record but the PDF lives in your shared drive or accounting tool. Reference the supplier invoice number for cross-system lookup. **What happens to a PO when the supplier is blocked?** Existing open POs continue. New POs cannot be raised against the blocked supplier. Unblock to resume buying. **Why is the Suppliers grid empty?** Either no suppliers have been added (use `Add Supplier`), or the filter is hiding them. Suppliers grid will show "No Records Found!!!" when nothing matches. **How do I deal with a supplier who supplies in a different currency than my workspace base?** Set the PO currency at creation. CloudHub stores the PO in the chosen currency. Reconcile in your finance system using the FX rate at invoice or payment date. ## Next steps * Set up your warehouses and bin locations under [Stock Locations](/vortex-apps/cloudhub/locate-warehouse/stock-locations). * Audit any quantity change with the [Stock Movement Log](/vortex-apps/cloudhub/locate-warehouse/stock-movement-log). * Configure user permissions for the buying team under [Permissions and Shipping](/vortex-apps/cloudhub/configure/permissions-and-shipping).