Track vessel requests, quotations, approvals, orders and invoices together. Technical fitness assessments and purchasing decisions remain with your authorized team.
In maritime procurement, a need arises at sea, technical staff validates it, shore teams collect quotes, management approves and delivery may occur at another port. Context is easily lost when this chain runs through email and spreadsheets.
Faromo keeps the requisition, RFQ, selected quotation, PO, one or more goods receipts and a supplier invoice tied to a single PO as related records. Stage, approval trail, delivery port and discrepancies remain visible throughout the process.
IMPA provides a common reference language for item identity, while current maritime procurement products describe requisition, RFQ, quotation, PO, receipt/inventory and invoice linkage as the shared category flow. The model below shows Faromo’s implemented behavior and the decision boundary at each step; it is not a universal procurement policy.[1][2][3][4]
A requisition line retains description, part number and technical specification; the six-digit IMPA code is optional. Faromo does not itself provide the licensed MSG catalogue, and a code does not verify equipment compatibility.
The requisition carries vessel, category, quantity, ROB, urgency, date and port; the RFQ carries invitations, scope, deadline, currency and supplier quotations.
The PO records the selected approved supplier and order lines; the GRN records received, accepted and rejected quantities. An inventory transaction is created only when a posted GRN has a stock location.
The current three-way control compares one PO, its posted GRNs and one supplier invoice; a record outside the match moves to DISPUTED rather than APPROVED.
Each row shows the application input, automated behavior, resulting record and the area where the product does not make the decision.
| Control point | Input | Faromo behavior | Resulting record | Decision boundary |
|---|---|---|---|---|
REQUISITION | Vessel, category, line item, quantity, ROB, urgency, required date and delivery port. | Moves the requisition through status and, when configured, applies vessel/shore or category-and-amount approval routing. | Numbered requisition, lines, approval or rejection trail and remarks. | Does not independently verify actual need, part compatibility or stock sufficiency across every store. |
RFQ | Invited suppliers; line price, currency, delivery days, validity and payment terms. | Records quotations and ranks them in the current internal model using 60% price + 40% lead time, with the lowest score ranked best. | RFQ-linked quotations and internal comparison ranking. | Does not decide technical fitness, quality, warranty, tax/freight or total landed cost. |
AWARD → PO | Selected quotation and approved supplier record. | Marks the selected quotation, rejects the others and creates an ISSUED PO; blocks the action for an unapproved supplier. | Purchase order linked to the RFQ and requisition. | Internal selection and PO creation do not replace company authority policy, supplier confirmation or legal contract review. |
GRN | PO lines; received, accepted and rejected quantity; date, port and optional stock location. | Prevents over-receipt, updates partial or full delivery state and writes a RECEIVE inventory transaction when a location is present. | One or more posted GRNs and inventory transactions when applicable. | Internal goods receipt does not replace independent quality inspection, certificate control or external delivery documentation. |
3-WAY | One PO, posted GRNs and one supplier invoice linked to that PO. | Compares invoiced quantity with accepted GRN quantity, and line unit price plus header-to-line total using a default 2% tolerance. | APPROVED or DISPUTED invoice state with line-level discrepancies. | A single invoice spanning multiple POs is unsupported; this control is not tax, accounting, legal or payment approval. |
The 60/40 quotation ranking and 2% invoice tolerance are current product defaults; they should be reassessed against company policy, category and contract.
The checklist complements the traceable system record with the procurement team’s technical and commercial judgment.[1][2][3][4]
This checklist does not replace company procurement procedure, contract, tax/accounting, sanctions screening, quality or maker/class requirements.
Record vessel, category, line item, quantity, remaining on board, urgency, required date and delivery port; add an optional six-digit IMPA code.
Keep invited suppliers, quoted lines, currency, lead time, validity and payment terms on the same RFQ.
The current model ranks quotations using 60% price and 40% lead time; the buyer completes technical fitness, quality and total-cost review.
Apply base-currency amount, authorized roles and required co-signers in a default or category-specific chain.
Create a PO only for an approved supplier, track shipment stages and record accepted or rejected quantities across multiple GRNs.
Compare a single-PO invoice with the PO and posted GRNs; route quantity or price variances beyond the default 2% tolerance to dispute.
Faromo ranks quotations in the current internal model using 60% price and 40% lead time, creates POs only for approved suppliers, supports partial GRNs and routes invoice variances to dispute using a default 2% tolerance.
The current web requisition entry requires connectivity. Offline procurement coverage is not claimed generally until it is separately verified by client and action during the pilot.
Yes. A default or category-specific chain can be configured with amount thresholds in the base currency, authorized roles and required co-signers. Currency conversion and company authority policy must be managed separately.
Yes. Order lines can be received in different quantities or dates while the open balance remains visible.
The requisition-line data model carries equipment and maintenance-job links. Because the current general web requisition form does not expose these fields directly, automatic end-to-end linkage must be verified through integration or additional UI scope.
No. The current control compares one PO, posted GRNs and the invoice for quantity and price, producing APPROVED or DISPUTED. Tax, accounting, legal and payment approval are separate; one invoice spanning multiple POs is unsupported.