What Everstock does, and what it will never do

Getting startedUpdated 23 September 2026

Everstock connects a supplier's feed to your Shopify store and keeps your stock in step with it. It reads the feed, works out what would change, lets you see that list first, and then writes only what you asked it to write.

Where the feed can come from

Everstock can read three kinds of supplier feed:

  • A REST API feed, set up by hand or from a supplier preset.
  • A WooCommerce store.
  • A CSV or spreadsheet file: a hosted file, a Google Sheet, an upload, or a file on FTP or SFTP.

See Connect your first supplier.

What Everstock syncs

Stock is the core of the app. It is on for every new connection, and for many stores it is the only thing they ever need.

Everything else is optional and starts off for products you already have:

Everstock matches supplier records to your products by barcode first, then SKU. That rule is fixed. You do choose the Shopify location: each connection reads and writes stock at one location. It syncs the available quantity there, which is the stock your storefront can sell.

What it will never do

A short, empty or broken feed can never zero your stock. Every sync sorts records into three groups: records that need a write, records that are already right, and records a person should look at. A product this connection synced before that is missing from today's feed goes to review, and any other product in your store is left alone. Neither ever gets a stock write, and neither ever becomes a zero.

More safety checks work the same way. A row whose quantity is blank or unreadable is skipped, and your stock is left alone. A run that would set a large share of your stock to zero, or a feed that suddenly looks very different from last time, is held before anything is written.

Everstock never publishes a product for you. Products it creates are always drafts.

Everstock only adds. It never deletes a product, a variant or an image, and never takes a product out of a collection.

Everstock never writes to your supplier. It reads the supplier's feed and writes to Shopify, one way only.

Everstock never sees your orders or your customers. It asks for exactly seven Shopify permissions: read_inventory, read_locations, read_products, read_publications, write_inventory, write_products and write_publications. The two publications permissions are used only to publish new collections when you turn that on. Supplier credentials and Shopify tokens are encrypted at rest. See Security, data and the permissions Everstock asks for.

The home page

The app opens on its home page, called Dashboard in the app's menu.

Until you have connected a supplier and run a sync, a Setup guide at the top walks you through the two steps: Connect a supplier and Run your first sync. You can collapse it or dismiss it.

The Overview section shows your plan as a badge, and five tiles for the last 7 days: Connections, Items applied, Success rate, Failed runs and Next sync. Click a tile to open the matching page. Below it, Needs attention lists failed runs and items for review when there are any, and Recent sync runs shows your latest runs.

At the bottom, More apps from Normalize lists other apps we make. Click the close button to hide it.

The shape of the workflow

  1. On Connections, click Connect supplier and fill in the form.
  2. Click Test connection. It reads a sample and tries your mapping. It writes nothing.
  3. Save with Save in the Shopify admin save bar.
  4. On the connection page, click Preview changes. This is a full dry run against your store. It opens "Preview: proposed changes" with the banner "Nothing has been written to Shopify".
  5. When the changes look right, click Sync now.

Reading the audit trail

Every run, preview or real, is listed in Sync history. Open a run to see the Run summary counts (Fetched, Applied, Skipped, For review, Failed), the Fetch log, and the Per-record audit, which you can filter by status.

If a real run wrote something you did not want, you can undo it for 30 days with Revert run or Revert product. A revert is always previewed first. See Read the per-record audit trail.

Look at the For review count when the numbers are not what you expected. See What "For review" means.

Need help? Visit the support page or email hello@usenormalize.com.