Order Desk questions,
answered.

Order Desk helps your team turn the purchase order documents it receives into reviewed Shopify draft orders. It brings the order details into a workspace where you can check the customer, products, quantities, prices and delivery location before approving.

The goal is to reduce repetitive entry while keeping the important decisions with your team. Suggested matches and extracted details remain part of a review process; the final output is a draft in the connected Shopify store, ready for the next step in your operation.

One document can contain several purchase orders. Each distinct PO needs its own PO number, customer, delivery location and line items kept together for review. For example, a document containing 11 POs should become 11 separately reviewable orders, rather than one combined order.

Capacity depends on more than the number of POs: a short order with a few items is different from a long scanned order, and a spreadsheet is organized differently from a PDF. During onboarding, we check representative documents and confirm a workable batch size for your team. The app enforces its current file and grouping limits at upload and review.

Order Desk accepts several file formats. The current pilot’s explicit multi-PO separation screen uses PDF page groups, which you confirm before preparation. Excel, CSV, image and email-text inputs use their existing extraction path; independently separating multiple POs in those formats needs to be checked with us first. For larger recurring batches, we validate your source formats and review workflow before agreeing on capacity.

Each separate PO record keeps the destination and line items extracted for that order. Your reviewer checks that the PO number, customer and ship-to address belong together before approving it. That distinction matters when the same buyer sends orders for several branches.

The usual case is one location per PO. In the less common case where one PO explicitly includes several destinations, those destinations can be reviewed separately and produce separate drafts while remaining part of the same PO. The document’s actual structure determines which case applies.

Order Desk evaluates the evidence available in the document against the connected store. For customer matching, buyer identity and destination information help distinguish plausible candidates. For products, SKU matching and supported formatting normalization help connect the source item to a catalog variant.

Confidence describes the strength of a recommendation; it is not a guarantee or a substitute for approval. A similar company name alone is not enough to confidently identify a delivery location. Ambiguous or conflicting evidence remains something for a reviewer to resolve.

This gives your team a practical way to focus attention: check the suggested match and its context, select another customer or product when needed, and resolve outstanding issues before approving the order.

Yes, where matching memory is enabled, a reviewer can explicitly save a confirmed customer or SKU match for future use. A saved customer match is tied to the buyer and destination context. A saved product match relates that buyer’s source SKU to a confirmed catalog variant.

For example, a buyer may repeatedly use its own item code for one of your products. After you select the correct variant and successfully save that match for future use, a later order with the same relevant context can benefit from that confirmed mapping.

Saved matches stay within the appropriate company and store context and are checked against current Shopify data. Missing entities, ambiguous SKUs or conflicting new evidence can prevent reuse. Reviewers can also forget a saved match. Editing a quantity or price does not automatically establish a permanent rule, and an ordinary correction is not the same as successfully saving matching memory.

You stay in the review workflow. Check the document and select the correct customer or catalog item, then verify quantity and price. Order Desk keeps uncertain matches visible so they can be addressed before creation.

The approval step does not remove the need for checks. Preflight evaluates whether the reviewed information is ready to create, and an unresolved issue can block creation. A high-confidence suggestion or a previously saved match does not mean an order should be accepted without review.

Yes. Reviewers can correct line-item quantities and select the appropriate pricing treatment, including the PO price, Shopify price or a custom draft price where the review controls support it. The purpose is to make the intended draft explicit before it is created.

Check each PO’s line items and total after making changes. A one-off price adjustment is specific to that order; it should not be confused with saving a reusable customer or SKU relationship. Your reviewer remains responsible for confirming the intended commercial details.

Approval requests creation of the reviewed draft order in your company’s connected Shopify store. In the usual one-location-per-PO workflow, each approved PO produces its own draft. Your workspace shows the result so your team can identify and open the corresponding Shopify draft.

Creating a draft does not collect payment, send an invoice or fulfill an order. Those are later actions in your operating process. If a request is interrupted and its outcome is uncertain, the safe next step is to check the recorded status and reconcile the result, rather than blindly create another draft.

The workspace is designed for use in a browser. Your team signs in to its company workspace to upload documents, review separate POs, approve drafts and inspect results. Shopify remains the destination for the draft orders.

The public website explains the product and provides the entry point. New companies receive an invitation after access is arranged. Use the secure workspace link provided during onboarding; the marketing preview itself is not a customer order-processing workspace.

You need access to your invited company workspace and a Shopify store owner or administrator authorized to approve the installation. The connection flow takes you to Shopify to review the permissions and authorize the correct store.

After returning, confirm the company and store identity before processing orders. No Shopify Admin token needs to be manually copied into Order Desk. The service also handles its AI integration, so your team does not need to create a separate Google API key or AI billing account.

Shopify is the first supported destination for customer and product matching and draft-order creation. That is the integration used for the current pilot workflow.

The connections page also shows planned systems, including QuickBooks Online, NetSuite, Dynamics 365, Xero, ShipStation, Cin7, BigCommerce and WooCommerce. These are roadmap directions, not currently available integrations or announced partnerships. We have not promised release dates.

Request a walkthrough and describe your current workflow. A representative document helps us understand how your POs are organized, how locations are identified and what your reviewers need to check.

If the pilot is a fit, we arrange your company’s access and provide the invitation and setup steps. You create your account, authorize the correct Shopify store and review an initial order together with the onboarding process. Access is currently invitation-only; submitting a request does not immediately create an account.

Processing time varies with the number of POs, pages and line items, the readability of the source and the checks needed against your store. A short, clear PO and a large scanned batch do not take the same amount of work. Each PO in a grouped PDF is prepared separately.

Preparation and human review are different stages. The app shows processing and readiness states; your team still needs time to confirm the customer, products, quantities and prices before approving. An uncertain match or an interrupted request may require additional review.

We do not yet publish a guaranteed seconds-per-PO figure or an end-to-end turnaround promise. During pilot onboarding, we time representative documents with your team so the expected processing time reflects your actual workload, rather than a best-case demo.

That is what it is designed for: customers sending purchase orders in different layouts, using their own item codes and describing locations in different ways. Order Desk accepts PDFs, Excel workbooks, CSVs, JPG/PNG images and text files, bringing supported documents into the same review workflow instead of requiring every customer to use one template. For orders received by email, upload a supported attachment or save the email’s order content as a text file. Direct mailbox syncing and native email-file uploads are not part of the current pilot.

Customer and SKU matching, supported formatting normalization and explicitly saved matching corrections help it fit your operation. Your team decides which customer, product and price belong on the order. A saved match is scoped to its company, store and relevant buyer context; it is not a rule applied indiscriminately to every document.

Flexible does not mean every file can be read correctly without help. Poor scans, illegible content, overlapping information and unsupported document structures still need attention. We check representative examples during onboarding, keep uncertainty visible and preserve approval checks rather than hiding an unreliable result.