Arrive
A PO reaches STRYKE the way it reaches you today: a PDF attached to an email, forwarded to your intake address or read from a mailbox you connected; a fax-to-email wrapper; a portal notification; an EDI 850 from the VAN mailbox or Web-EDI inbox you already have; a file dropped by SFTP. Nothing changes for the buyer. The first thing STRYKE does is store the original exactly as it arrived, with who sent it and when. That copy stays attached to everything that follows.
Who sent it matters. A document from a sender your shop has done business with is read. A PO from an address no customer of yours has ever used is held before anyone acts on it, which is how a spoofed PO ends up on a list instead of in your ERP.
Read
STRYKE reads the whole document, not just the header: the PO number, the ship-to, the terms, and every line with its part number, description, revision, quantity, unit and price. Each field carries a confidence. The usual run of POs reads above the line your shop sets (0.9 by default) and goes on; a smudged fax or a line that reads two ways does not, and that document waits for a person.
Match
Then every line is matched to your records. The customer's part number becomes yours through that customer's own cross-reference, learned from the Orders you have already entered, so a 77-120-01 lands on your A-77120-01 without anyone keeping a table. The price is compared to the quote the PO came from, or to the price list. The ship-to and dock are checked against what the ERP already knows for that account. Where STRYKE can ask the ERP, it does: an Odoo partner lookup through Odoo's external API or a JobBOSS² customer read happens while the document is being read.
Check
Before anything is written, the document is checked the way your order desk checks it. Is this the same PO as one that already arrived, by email this morning and by fax this afternoon? Does quantity times price equal the extended total? Is the revision on the line the one your ERP has, or a new one? Is a due date earlier than you have ever shipped that part? Each check that fails is a hold, and the hold says why.
Enter
A PO that passes becomes an Order in your ERP, with the customer PO number, lines, revision, quantity, unit price and due date, and the Job your ERP creates from it. Through JobBOSS²'s API or Odoo's, the Order is written and read back, so STRYKE knows its number. Through an import file, STRYKE writes one CSV per entry and your import map takes it. Through the desktop runner, STRYKE's runner on a shop PC keys the entry into the ERP's own screens. Those two doors cannot ask the ERP whether this PO was already entered, so the duplicate check waits for a person's one click before the entry goes.
What a PO becomes depends on the system: an Order and its Job in JobBOSS², a sales order with its partner in Odoo. The original, what was read from it and any correction a person made stay attached to the entry. Purchase order processing has the detail for each system a job shop runs.
Answer
The buyer asked for an acknowledgment. It goes out from the Order, not from a person remembering: a reply in the buyer's own email thread, under your name, with the promise date; an 855 for an 850, with the 997 that confirmed receipt; an order confirmation in the portal for a portal PO. A change order later brings a revised acknowledgment, from the revised Order.
What stops, and what never goes on its own
Most POs go straight through. The ones that do not are on a short list on your Home page, each with its reason: a price off the quote, a part number STRYKE has not seen, a date pulled in, a total that does not add up, a sender no one vouched for. A person picks the answer and the Order goes in with it; the answer becomes a rule for that account, so the same question is not asked twice.
Some things are never automated, however confident the read. A promise is one: a date pulled in, a price moved, a new part, new bank details on a vendor invoice. STRYKE enters what the document says and what your records agree with; it does not agree to something new on your behalf. That is the line between an order desk that has been retired and one that has been replaced by something that guesses, and the product page shows where the line sits on the screen.