All FAQ guides

FAQ / Shopify operations

Connect the order to the shipment

An order is only the beginning. Randmar’s fulfillment job connects eligible Shopify fulfillment requests with Randmar ordering, then sends matched shipment quantities and tracking back to Shopify.

Shopify operations · 03 / 05

Behind the workflow: ExecuteShopifyFulfillmentToStore

Before this job can act

Prerequisites for your store

  • The Shopify hostname must identify a linked store with usable access. The job operates on fulfillment orders assigned to the service, not every ordinary Shopify order.
  • SyncOrders controls automatic submission of eligible open, unsubmitted requests. Turning it off does not stop handling already-submitted requests, cancellations or shipment synchronization.
  • For a new Randmar order, the account must not be on hold. Items must resolve to supported products, and a valid cart and shipping details must be available.
  • To report a shipment, the processor needs shipment/invoice details, matching remaining Shopify line quantities and usable tracking information for a supported carrier.
  • New order processing needs a supported shipping destination. This code accepts Canada and the United States with address validation, and rejects other country codes; that is not a promise of service eligibility or rates for every destination.
  • The worker must be enabled for this job and the connected services must permit the required operations. This article does not confirm your store’s live permissions or schedule.
AI-generated editorial image of a worker packing a kraft shipping carton at a dispatch bench
AI-generated editorial image illustrating order packing and fulfillment.
The purpose

Two directions, one order workflow

The first direction is from Shopify to Randmar. The processor reads fulfillment requests, checks account and product information, and builds a Randmar order for eligible requests. It looks for an existing order with the same purchase order reference to reduce repeat entry.

The second direction is from Randmar back to Shopify. Shipment and invoice documents provide the evidence for shipped quantities. The processor matches those quantities to the remaining fulfillment lines and creates Shopify fulfillment records with tracking.

What it can change

  • Eligible request status, Randmar cart/order creation and explanatory Shopify order notes where needed.
  • Shopify fulfillment records for matched shipped quantities, including partial shipments and tracking.
  • The order’s randmar.synced_documents metafield, which records processed shipment/invoice documents. Cancellation request handling can change the request/order outcome.
  • Can submit, accept or reject requests and add order references, tags, custom attributes and notes. A preexisting Randmar cart with the same PO/cart name may be removed before processing.
  • Customer shipment notification follows the request’s notify_customer option. It is not unconditionally enabled.

What it leaves alone

  • Product marketing content, images and the store’s catalogue selection.
  • Already-shipped quantities are reconciled before cancellation. The cancellation path does not undo a shipment.
  • Existing Randmar orders identified by purchase order reference are reused rather than deliberately entered again. This reduces duplicates but is not an exactly-once guarantee.
Skipped, stopped or partly done

Exceptions you should know

  • An account hold pauses new order entry and adds an explanatory note. Unmatched products, unavailable stock or cart failures can prevent an individual order from proceeding.
  • With ShipComplete enabled, if any required line has insufficient available quantity, the fulfillment request is rejected. This path does not accept the other lines as a partial order.
  • Supported tracking mappings in the reviewed code are Canpar, Canada Post, Purolator, UPS and FedEx. Unsupported carriers, incomplete tracking or quantity mismatches can require attention.
  • A fully shipped order has cancellation rejected. Cancelling an unshipped remainder depends on Randmar cancellation succeeding; a failed cancellation can need human intervention.
  • Some order/document errors are logged and skipped while the job continues. Overall job completion is not proof that every request or shipment succeeded.
  • Processed-document marking follows fulfillment creation. A failure between those steps means the stored document marker alone is not a perfect duplicate-prevention guarantee.
  • The job reads the first 250 assigned fulfillment orders without pagination. Reaching 250 line items on a fulfillment order or its Shopify order triggers failure.
  • ShipComplete is an availability gate before ordering, not a guarantee of one physical shipment. Cart processing permits partial shipment. Turning ShipComplete off still leaves product, cart and address checks in place.
  • Rejected requests and cancelled/incomplete fulfillment orders are skipped. A closed Shopify order triggers an attempt to cancel its fulfillment order.
  • An ambiguous manufacturer-part-number match can be rejected with guidance to add the correct UPC/barcode. Matched shipment lines may still be fulfilled even when other quantities do not match.
How the job connects the steps

From request to fulfillment record

Process graph · conceptual sequence

  1. Shopify requestEligible order lines
  2. Randmar orderAccount, stock and cart checks
  3. Shipment evidenceShipment or invoice documents
  4. Shopify fulfillmentMatched quantity + tracking

Arrows describe the workflow. They do not represent elapsed time, throughput or a guaranteed outcome.

How to check the result

  1. Match the Shopify request to the Randmar order using its purchase order reference and inspect account/cart exceptions.
  2. Compare each fulfilled quantity with shipment evidence and the remaining Shopify line quantity; check the tracking link and carrier.
  3. For cancellations, confirm the actual unshipped remainder was cancelled and inspect any rejection or escalation.

A shipment record should tell the same story

Verify the order reference, fulfilled quantities and tracking together. They describe what actually moved, including partial fulfillment, rather than simply marking an order complete.

Scope of this explanation

Behavior verified against the reviewed local source baseline on 4 November 2026. The default worker configuration excludes these Shopify jobs; a runtime configuration must enable them. Live deployment, scheduling and your store’s settings were not verified. No update interval or real-time service guarantee is implied.

Further reading

Prepared 4 November 2026