A customer PO arrives by email, fax, a portal or EDI, and someone on the order desk types it into the ERP. STRYKE does that step. It reads the PO, matches each line to your part numbers and your quote, enters the Order, and replies to the buyer with the ship date.
What arrives
Customer purchase orders come in five ways, and each customer picks their own.
A PDF attached to an email from a buyer's Outlook, SAP, Oracle or QuickBooks
A portal notification from Ariba, Coupa, Jaggaer or Oracle iSupplier with a Process Order button and the PO attached
An EDI 850, or a release against a blanket, through a VAN or a Web-EDI inbox
A fax-to-email wrapper with a black-and-white scan of the PO
A phone call, a voicemail or a text with a photo of the part, for repeat orders
What STRYKE does
STRYKE reads the whole document, not just the header, and checks it before anything is entered.
Each line is matched to your part number through the customer's own cross-reference, with revision and unit of measure checked
The price on the PO is compared to your quote or price list; a difference is held, not entered
The same PO sent twice, once by email and once by fax, is caught as a duplicate
Ship-to, dock, terms and the acknowledgment deadline come from what you already know about that account
Anything STRYKE is not sure of waits on a short review list for a one-click confirm
Where it lands
The Order is entered in your ERP the way your person would have entered it, from one read.
An Order with the customer PO number, lines, revision, quantity, unit price and due date in JobBOSS², E2, Epicor, Global Shop, ProShop or the ERP you run
A new Job where your ERP creates one from the Order
The original PO, what was read from it and any correction stay attached to the Order
Where the ERP has an API, STRYKE uses it; where it has an import, it uses that
What goes back out
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 with the promise date, under your name
An EDI 855 for an 850, with the 997 that confirms receipt
An order confirmation in Ariba or Coupa for a portal PO
A revised acknowledgment when a change order moves a quantity or a date
“We get sixty-some customer POs a month, about a third of them faxed. Before, every one of them was ten minutes of my day. Now the review list is three or four lines a day, usually a price that moved, and the acknowledgment is in the buyer's inbox before they think to call.”
Questions shops ask
What if the customer uses their own part numbers?
That is the normal case. STRYKE learns each customer's part-number format from the Orders you already entered, so a customer's 77-120-01 lands on your A-77120-01 without a cross-reference table anyone has to maintain. A number it has never seen is held for a person, and the answer becomes a rule.
What happens when the price on the PO does not match our quote?
The line is held. STRYKE enters nothing silently when the price, the unit of measure or the revision differs from your records. The review list shows the PO line next to the quote, a person picks one, and the Order goes in with that answer.
Does the buyer have to change anything?
No. Email, fax, portal, EDI and phone all keep arriving the way they do today. STRYKE sits on your side of every channel; there is no portal to push onto a customer and no EDI project for a small account.
$500 a month, flat
Every customer PO, however many. Not per document, not per seat, not per system. Month to month. What the one price covers.
