Support › Catalog

How the daily run works

Short answer

Once a day, after EJD's new files arrive, the app plans your store's changes, holds anything unusual for you, then adds new products, makes updates and drafts discontinued items.

Once a day, after EJD's new files arrive, the app compares them with your store and plans the changes. Anything unusual is held for you to decide. The rest is applied in a fixed order: new products, then updates, then discontinued items. Nothing is ever deleted.

New to words like ECOM, BRICK or RRP? See the glossary.

What happens, step by step

  1. EJD's files arrive. Your store's catalog comes from your own EJD account: its files say which items you can get and what you pay. Product details (titles, photos, specs, suggested prices) come from one shared catalog Striven keeps. A file that fails the app's checks isn't used. See Your EJD logins.

  2. The run starts on its own, shortly after a new file arrives, usually in the morning. To start one sooner, select Start a run now on Catalog.

  3. The app compares. It reads your store's products, drafts included, and compares them with EJD's newest files and your settings. Every planned change is listed on the run.

  4. Safety checks. If the run looks wrong, it stops and changes nothing. You can set these limits in Settings > Pricing and safety:

    • Stop if discontinued above (%): default 5%.
    • Stop if moving online/store-only above (%): default 3%.
    • The run also stops if EJD's file is more than 10% smaller than the number of EJD items in your store. This limit is fixed.
    • Hold cost changes above (%): default 100%, a cost that doubles or halves. Those items are held for you; the rest of the run goes ahead.

    See Today's run stopped.

  5. Held changes wait on the run's Held tab. For each one, choose Approve, Skip or Pull item. The other changes don't wait for them. See Deciding on held changes.

  6. Apply. What happens depends on When writes are on and a run passes every check, in Settings > Updates and new arrivals:

    • Wait for me to apply each run: open the run on Catalog, select Apply (the button shows how many changes), and confirm.
    • Apply it automatically, except what I choose below: the run applies by itself. Held changes, and the kinds of change you chose to review, still wait for you. See What updates on its own.
  7. After it's applied, the app updates collections, menus, filters, search text, images and Google Shopping to match, for the features on your plan.

The changes are always written in this order:

  1. New products
  2. Updates: cost, price, case size, shipping profile, tags, hidden and restored items
  3. Discontinued items: set to draft, never deleted

New products go live once their shipping profile is set. To check them first, choose Create them as drafts for me to review under New products from EJD in Settings > Updates and new arrivals. Store-only items (ones EJD only delivers to your store) follow your choice for them on Rules: hidden, shown but not for sale online, or sold from your own shelf.

In compare mode nothing is written. The run is planned and shown as Compared, so you can see what it would have done.

Deciding on held changes

What Approve does depends on where the run is. The Held tab says which applies:

The run is Approve Skip
Needs review The change is added to the run and written when you apply it. Left out of this run.
Applying Written right after the run finishes applying. Not written.
Finished (including runs your store applied automatically) Written to your store right away, in the background. Undoing the run puts it back too. Not written.
Failed, Undone, Superseded, Stopped or Compared Not available. Not available.

To decide on a whole group at once, use Approve all or Skip all above the list. Approve all asks you to confirm first, with the count and a few of the changes.

Once a newer run is planned, decide on the newer run's Held tab instead. The older run's held changes can't be approved any more, and approvals it hadn't written yet show as Skipped: the newer run checks each item again from EJD's latest files.

A change you skip, or don't decide on, isn't lost. If it still needs a decision, the next run holds it again. For example, an unusual cost change stays held until you approve it or EJD's cost goes back.

While writes are paused, approved changes wait and are written right after you resume. If they're still waiting later, the run shows how many with a Write approved changes button.

Some holds can't be approved, because the next run would undo the decision or something has to exist first. The Held tab says what to do instead:

  • Pulled: remove the item from the pull list on Products.
  • Not for resale: it stays off your store.
  • Brand not approved: take the vendor off your list in Settings > Pricing and safety.
  • Bulk-unit mismatch: add the Sell by the case add-on to list it as the pack.
  • Shipping profile missing: create the profile in Shopify. See Shipping profiles.

Why that order

New products must exist before updates refer to them. Discontinuing last means a bad file is caught by the stop limit before anything is hidden.

Run statuses

Status What it means
Planning The app is comparing EJD's files with your store. This takes a few minutes.
Stopped A safety check failed. Nothing was written.
Needs review Planned and waiting for you to apply it.
Applying Being written to your store now. The run page and Home show progress.
Finished Applied. You can undo it.
Undoing You asked to undo it, and the app is putting back the saved values.
Compared Planned in compare mode. Nothing was written.
Failed Stopped partway through writing. What was written is recorded and can be undone.
Undone Undone. Your store has the values from before it, except protections and items a newer run changed.
Superseded A newer run replaced it, or your plan changed. It can't be applied. Open the newest run instead.

Where to see it

  • Home shows the last run and anything waiting on you, with the five most urgent alerts. See all open alerts opens the full list, where you can dismiss an alert you've dealt with. It comes back if the problem happens again.
  • Catalog lists every run. Open one to see each change on its tabs, with a search by SKU or title.
  • Export on a run's tab downloads its changes as a spreadsheet, with the before and after numbers for each change.
  • Each run saves the values it replaced, so you can undo it.

Superseded runs

A run that's waiting to be applied, or was only compared, is marked Superseded once a newer run is planned or applied. It was planned from older data, so applying it could write yesterday's prices over today's. Its page links to the newest run: open that one. Nothing is lost. A change from a run that was never applied is planned again by the next one.

A run is also superseded if you changed to a plan with a different catalog between planning and applying it. The next run plans for the plan you have now.

Waiting for another update

Only one big update writes to your store at a time. If unique content or a restore is being written when a run is applied, the run says "Waiting for another update to your store to finish" and tries again on its own. Nothing is written until it starts. The same happens if another app is running a large update in your store.

Shopify's limit of 1,000 new products a day

Once a store has 50,000 product variants, Shopify lets it add only 1,000 new ones a day. A store loading EJD's whole online catalog can pass that. Each run then adds as many new products as Shopify allows that day, and the rest show as not written with the code CATALOG_DAILY_VARIANT_LIMIT. Nothing failed and nothing is paused: the next run adds the next 1,000, until the catalog is loaded. Updates to products already in your store aren't limited.

When writes are paused

If writes to your store are paused, runs are still planned. They wait as Needs review and say why. Apply the run after you resume, or let the next run apply. See Writes to your store are paused.

Technical details

Show the exact rules, for the technically minded
  • Where the data comes from. Your store's catalog is Striven's master catalog (EJD's content plus Striven's corrections) limited to the SKUs your own EJD account's files list, with your account's cost and future cost laid over it. National Hardware Group's store reads the master directly.
  • When files are collected. The app logs in to each of your EJD logins every 4 hours, plus a fixed offset of up to 30 minutes per login. A working login that starts failing is retried every 2 hours; one that failed when saved waits until it is saved again.
  • When a run starts. 5 minutes after a valid file arrives from your own login, and 20 minutes after a new shared file (EJD's catalog, restrictions file or state report), so ECOM and BRICK files that land minutes apart are read by one run.
  • What the file checks look at. The right account and warehouse, the expected columns, and a row count close to the last file's. A file from your login that would drop more than 5% (and at least 25) of the items your store carries from that channel is held for Striven to check with EJD. See Your EJD logins.
  • Stop limits. Discontinued: discontinued items ÷ your store's EJD items > the limit. Moving online/store-only: moves > the larger of 500 and the limit × your store's EJD items. File size: EJD's item count < 90% of your store's EJD items. Cost hold: new ÷ old cost above 1 + the limit, or below 1 ÷ (1 + the limit), so 100% catches a doubling or a halving.
  • The comparison baseline. Each run compares EJD's newest files with EJD's files as they were at the last applied run. A compared, waiting, paused or superseded run doesn't move that baseline, so EJD's changes add up until a run is applied. A skipped or unwritten change is planned again.
  • Waiting for another update. The run retries every 10 minutes.

Related

Still stuck? Open Help and support inside the app to ask about your own store or write to a person.