Randmar
All FAQ guides

FAQ / Shopify operations

Maintain the catalogue already in your store

“All products” describes a store-wide maintenance pass. This job finds matched, Randmar-tagged products already in Shopify and refreshes pricing and operational data according to the store’s settings.

Shopify operations · 04 / 05

Behind the workflow: SyncAllShopifyProductsToStore

Before this job can act

Prerequisites for your store

  • Use the correct linked Shopify hostname with usable Shopify access, Randmar product data and an existing Randmar.io fulfillment-service location.
  • Products must already be in Shopify, match supported Randmar identifiers or a defined virtual bundle, and carry the Randmar tag. This job does not import absent products.
  • Check the store’s pricing strategy before the run. The setting controls selling-price treatment.
  • Inventory sync controls quantity writes and tracking/location setup. Turning it off does not disable pricing and other operational maintenance.
  • 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 retailer reviewing catalogue records beside a printed product catalogue and calculator
AI-generated editorial image illustrating catalogue maintenance with a simulated interface.
The purpose

Maintain the assortment you already carry

A store-wide sync begins with the Shopify catalogue, not with an instruction to import every Randmar item. Existing products and variants are matched against Randmar’s product report using barcode and SKU identifiers, with support for defined virtual bundles.

Eligible matched products receive operational updates. Depending on the configuration and handler rules, these include selling price, cost, country of origin and inventory. Descriptive content is outside this invocation: it does not request a rewrite of titles, vendor, SEO or descriptions.

What it can change

  • Selling price according to the configured strategy, plus cost when the handler permits it and country of origin.
  • Inventory quantities and setup when enabled, including attempts to connect the Randmar location and enable tracking.
  • Eligible variant data within existing products. The update payload retains sibling variant IDs and options.

What it leaves alone

  • This invocation does not rewrite title, product type, vendor, SEO, description, media, barcode/SKU or weight. Compare-at price is not assigned in its inspected update payload.
  • Unmatched or untagged products, and products absent from Shopify. No entire-Randmar-catalogue import takes place.
  • This caller skips selling-price updates under DO_NOT_RESYNC. That behavior must not be assumed for selected-SKU hard updates.
Skipped, stopped or partly done

Exceptions you should know

  • MAP and MSRP use their base values directly in this baseline. Only the explicitly named MSRP_MINUS_DEFAULT_OPP and MAP_MINUS_DEFAULT_OPP strategies subtract the default opportunity discount.
  • DO_NOT_RESYNC is caller-specific. It is not a general lock on all product data or a guarantee that another workflow preserves the price.
  • Stores above 5,000 variants are split into four stable hash-based pages. One completed page does not establish that the whole catalogue is complete.
  • Inventory deactivation/tracking-disable cleanup is implemented for one specifically coded account; other accounts log intended cleanup. Do not assume that behavior is universal.
  • The final catalogue snapshot is taken from the earlier Shopify read, not a verified after-update export. Snapshot upload errors are logged without failing the sync.
  • Some bulk product errors are only logged, and inventory-setup errors are caught per item. A completed job can include products that failed to update.
  • Earlier writes can remain after later failure. The maintenance pass is not an atomic all-products transaction.
  • The exact DO_NOT_RESYNC value also suppresses cost refresh in this caller. Unusual casing has inconsistent handling in the reviewed implementation; use the supported configuration value rather than relying on case variations.
How the job connects the steps

A maintenance pass, not a catalogue import

Process graph · conceptual sequence

  1. Existing catalogueRead Shopify products and variants
  2. Match + filterRandmar identifiers and tag
  3. Operational updateConfigured price and inventory rules
  4. Continue if neededNext page for larger catalogues

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

How to check the result

  1. Check representative matched variants for selling price, cost, country of origin and the intended location quantity.
  2. Confirm that all pages or scheduled continuation have finished for a larger catalogue.
  3. Use Shopify’s actual current state to verify changes; do not treat the attached snapshot alone as post-update proof.

Keep the assortment stable while the data changes

Use this workflow to maintain an established Randmar assortment. Confirm pricing settings and inspect representative variants after the run, especially when inventory setup or catalogue size changes.

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