Randmar
All FAQ guides

FAQ / Shopify operations

Bring selected Randmar products into Shopify

Start with the products you want to sell. Randmar’s selected-product sync takes a list of SKUs, creates missing Shopify products and refreshes eligible existing listings.

Shopify operations · 05 / 05

Behind the workflow: SyncShopifyProducts

Before this job can act

Prerequisites for your store

  • Provide a nonempty Randmar SKU list and the correct linked Shopify hostname, with usable Shopify access, the Randmar location and product-report data.
  • The job must be in a supported active state: the processor proceeds for Running or Scheduled jobs.
  • For an existing-product refresh, the product must have a single variant and no populated custom.spec1 field. The matched Randmar source record must contain manufacturer name, manufacturer part number and title; these need not already be filled in Shopify.
  • Review the selected SKUs and the broad update scope before running. This path performs hard updates and explicitly enables quantity writes.
  • 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 hands selecting a navy mouse for a tray beside a mug and notebook
AI-generated editorial image illustrating selection of a store assortment.
The purpose

An explicit selection, not every product

The input is a nonempty list of Randmar SKUs and a linked Shopify hostname. The processor reads the store catalogue and Randmar’s product report, then decides whether each requested product needs to be created or can be refreshed.

For eligible existing single-variant products, the refresh is broad. It can cover title, product type, vendor, tags, SEO, description, identifiers, price, inventory, cost, origin, weight and tracking setup. That scope makes selection and review important.

What it can change

  • Creates absent products with ACTIVE status and attempts to publish them to the Online Store. This is not an import-to-draft workflow.
  • For eligible existing single-variant products, hard-updates source title, type, vendor, merged tags, SEO, description, barcode/SKU, price, inventory, cost, origin and weight. It sets tracking and shipping-required flags.
  • Requests separate media processing for eligible processed SKUs. Scheduled selected-SKU jobs for the same store may be combined into a replacement job.

What it leaves alone

  • Existing multi-variant products are skipped by this update path.
  • Existing products with a populated custom.spec1 field are skipped, protecting that curated update path.
  • Products outside the effective requested selection are not the intended scope. Same-store scheduled-job merging can expand that selection to other pending requested SKUs.
Skipped, stopped or partly done

Exceptions you should know

  • DO_NOT_RESYNC is not a universal price lock. This selected-SKU hard-update caller does not supply the selling-price skip flag used by store-wide maintenance.
  • Missing manufacturer name, manufacturer part number or title prevents an existing-product update. A no-match SKU request fails; partially missing SKU lists are not comprehensively reported.
  • Duplicate SKUs are explicitly removed when scheduled jobs are merged. Do not assume every ordinary input list is independently deduplicated.
  • Creation and update batches are processed separately, and media is requested later. A product can exist or be updated before its media work finishes.
  • Stopping schedules remaining work. Check continuation rather than assuming an interrupted run completed every SKU.
  • Routine inventory sync disabled does not protect quantities here. This path explicitly enables quantity writes and configures inventory/tracking during creation.
  • An existing product does not need a Randmar tag to be refreshed; this path can add the tag.
  • Under DO_NOT_RESYNC, this caller may use MSRP and refresh cost because it does not pass the selling-price skip flag. Do not use that setting as protection against this job.
  • New-product publication can fail while creation remains successful. Check status and actual Online Store availability separately.
  • Some creation/update errors are logged without failing the whole job, and media may still be requested. Earlier batches can remain changed after a later error.
  • There is no equivalent comprehensive source-field validation for creation. Shopify can reject an incomplete new-product payload.
How the job connects the steps

The selected-SKU decision path

Process graph · conceptual sequence

  1. Requested SKUsSelected SKUs for one store
  2. Check the catalogueDoes each product already exist?
  3. Create / refresh / skipApply eligibility and content checks
  4. Request mediaSeparate follow-up processing

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

How to check the result

  1. Compare the effective requested SKU list with products actually created, refreshed or skipped. Review pending same-store requests if jobs were merged.
  2. For each changed product, inspect content, identifiers, price and location inventory. Pay special attention to curated pages and manually set prices.
  3. Verify the separate media request finished, and resolve missing or skipped SKUs individually.

Curate first. Verify the result.

Choose the assortment that fits your customers, then check the created or refreshed products, their prices, inventory and media. A successful catalogue request is the start of that verification, not a substitute for it.

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