Skip to content

Availability

Verified

An availability is what a shop shows customers next to a product, such as In stock, Backorder or Preorder. On the Availability screen you match them across your shops so that a change to a product’s availability carries over everywhere, and on the Manage tab you maintain each shop’s availability list without signing in to the shop admin. Nothing is written to a shop that you have not seen in a preview first.

Where to find it in the app: Operations → Warehouse | Products → Availability

The screen has three tabs:

  • Matching (opens first): which availability in one shop corresponds to which one in the others, and the switch that turns availability sync on.
  • Manage: the availability list of every connected shop, change proposals waiting for approval and the recent changes to the lists.
  • History: what the sync carried over to which shop, and with what result.

Load from stores reloads the availabilities from all shops, for example after you created a new one directly in a shop’s admin.

Every shop has its own availability list. An entry has these fields:

Field What it means
Name The text the customer sees, in the shop’s language. A name cannot repeat within one shop. Up to 120 characters.
Description Extra text shown to the customer with the availability. Up to 1000 characters.
Restocking in hours In how many hours the goods will be in stock. Search engines use it to estimate availability. A whole number from 0 to 2500, or empty.
Delivery in hours In how many hours you deliver the goods to the customer. A whole number from 0 to 2500, or empty.
Google Shopping The meaning of the availability: In stock, Backorder, Preorder or Out of stock. It decides what the shop reports to Google Shopping and whether a product can still be ordered once it sells out.
Color The colour the shop highlights the availability with, or none.

Entries carry labels:

  • system: an availability supplied by the shop platform itself;
  • default in stock, default sold out with ordering, default sold out without ordering: the shop uses it as the default in that situation;
  • in pairing: how many matching rows the availability is in.

An availability is not a stock level. How much of a product you have is on the Stock sync screen, see Stock and products.

The Matching tab makes sense once two or more shops are connected. Each row is one availability across your shops, and in each shop you pick the entry that corresponds to it. The main states (In stock, Preorder, Backorder, Out of stock) can be filled in from suggestions the app prepares from the Google Shopping meaning and the shop’s default availabilities. For special cases, such as a preorder with a specific date, you add a custom row.

After saving the matching you turn on Availability sync; it can be switched on once at least one availability is matched in two shops. From then on, a change to a product’s availability in stock or when sold out, made in the shop admin or in MitoOps (product card, bulk edit, availability plan), carries over to the other shops that have a product with the same code; variants are matched by variant code. Turning sync on does not overwrite anything by itself: only changes made afterwards carry over, each one is listed on the History tab, and history is kept for 12 months. An availability that is not in any row is not carried over.

For every shop the tab lists its availabilities with name, meaning, restocking, delivery and labels. Whether a shop’s list can be changed depends on its platform (see Differences by platform below); when it cannot, the tab says so next to the shop and the availabilities are read-only.

While the Matching tab has unsaved changes, the list cannot be changed. Save or discard the matching first.

Add availability sits next to each shop separately, because the name and description are in that shop’s language. Fill in the fields from the table above; a new availability needs a name and a Google Shopping meaning. Then press Show preview.

Edit next to an availability opens the same form. Only what you actually changed is sent to the shop.

For a bulk edit, tick the availabilities you want, across different shops if you like (the box in a shop’s table header selects the whole shop), and press Bulk edit. You can change the Google Shopping meaning, the colour (keep it, remove it or set a new one) and the restocking and delivery hours. An empty field or Keep leaves the value as it is. Name and description are never changed in bulk, because they are in each shop’s own language.

Only your own availabilities can be deleted. Delete will not remove:

  • a system availability, which the shop does not delete;
  • a default availability; set a different default in the shop admin first;
  • an availability used by an availability plan; cancel the plan first or wait until it ends.

If products still use the availability, the shop refuses to delete it and the result says so; give those products a different availability first. If the availability is in a matching row, deleting it removes it from the matching too. A deletion cannot be undone and also requires the right to delete products.

Every change, single or bulk, goes through the same three steps:

  1. The preview is prepared by the server: for each entry it shows every field before and after the change, warnings (for example that a new meaning changes what the shop reports to Google Shopping and whether products can be ordered once sold out, or that export files with the old name will match a renamed availability only after the product catalogue is refreshed) and blocking errors to fix. Nothing has been written yet.
  2. Write to shops sends exactly what the preview showed. A preview is valid for 10 minutes; when it expires, prepare it again. If the shop’s list has changed in the meantime (someone edited it in the shop admin), nothing is written and the app asks you for a new preview.
  3. The result per entry: written, written (verified by reading the shop), unclear, check the shop or not written, with the reason.

When a shop does not answer clearly (an error on its side, a timeout), the write is not repeated, because it may have gone through. The app checks it by reading the shop’s list again. Whatever cannot be verified stays unclear and needs a look in the shop. At most 30 entries can be changed at once.

A model can propose a change to the list too: the MitoOps assistant, or an AI application connected over MCP such as Claude.ai that you granted the Availability: change proposals scope. It prepares a proposal only for a person who could also approve it, and it writes nothing to the shop. The proposal appears on the Manage tab under Draft changes pending approval, and the Matching tab points to waiting proposals with an Open Manage button.

For each proposal you see who prepared it, where it came from (MCP or assistant), how long it is valid and the full preview. Then:

  • Approve and write writes the proposal to the shop with your permissions at that moment, exactly like a write from the screen. A proposal that deletes something can only be approved by someone allowed to delete products.
  • Reject discards the proposal and nothing is written to the shop.

A proposal is valid for 24 hours; after that it expires and is not written. If the shop’s list has changed since the proposal was prepared, approving it writes nothing and the proposal ends as not written. The model can read the status of the proposal, so after approval it can also tell you the result. The technical details are in the MCP interface.

The expandable Recent registry changes list shows the latest writes to the availability lists: time, shop, availability, action (new availability, edit, delete), result, who started the write, where from (screen, MCP, assistant) and, for an approved proposal, who proposed it. The records are kept for 12 months.

Platform What is possible
Shoptet The list is managed directly through the Shoptet API. The shop access must allow changing availabilities. A system availability cannot be deleted; Shoptet accepts edits to it, but the preview warns that the shop has not confirmed such an edit yet, and if the shop rejects it nothing changes.
WooCommerce with the MitoOps plugin The list is kept by the MitoOps for WooCommerce plugin, which you download under Integrations and install in WordPress. The shop key must belong to a user who can manage the store. The meaning of a system availability (a WooCommerce core stock status) does not change, and the meaning of a default availability must fit its role. Changing a meaning requires plugin 1.5.0 or later: after the change it immediately updates the products and variations that use the availability (whether they can be ordered once sold out and, without stock management, their stock status) and reports how many products and variations use it.
WooCommerce without the plugin The shop has only the three WooCommerce core stock statuses: In stock, On backorder and Out of stock. The list is read-only and the Manage tab recommends installing the plugin.

Default availabilities (in stock, sold out with ordering and without it) are set in the shop admin, not in MitoOps. Shoptet does not allow setting them through its API.

Action Required rights By default
View all three tabs Stock sync: read Warehouse worker, Manager, Administrator
Change the matching, turn sync on or off Stock sync: settings Manager, Administrator
Add and edit an availability, approve or reject a proposal Stock sync: settings and Products: edit Manager, Administrator
Delete an availability, approve a proposal that deletes additionally Products: delete Manager, Administrator

Anyone without the rights to change things sees the availabilities read-only, and the screen says so. Rights can be granted one by one, see Users and roles.

  1. Open Warehouse | Products → Availability and go to the Manage tab.
  2. Next to the shop, press Add availability and fill in the name, the Google Shopping meaning and, if needed, the description, hours and colour.
  3. Press Show preview and check the change and the warnings.
  4. Press Write to shops.
  5. In the result, check that the entry is written. The new availability appears in the shop’s list and under Recent registry changes; if it should carry over between shops, put it into a row on the Matching tab and save the matching.
  • The edit buttons are missing. You lack the right to manage stock sync or to edit products. Delete also requires the right to delete products.
  • A WooCommerce shop’s availabilities cannot be changed. The shop does not have the MitoOps plugin. Download it under Integrations and install it in WordPress.
  • Changing a meaning on WooCommerce failed with a plugin version error. Update the MitoOps plugin in the shop admin to 1.5.0 or later.
  • The shop key has no permission to change availabilities. On WooCommerce you need a key of a user who can manage the store; on Shoptet, access that allows changing availabilities.
  • Not written: the shop’s list changed since the preview. Someone edited the availabilities in the shop admin in the meantime. Prepare the preview again.
  • The result says unclear. The shop did not answer clearly and the write could not be verified. Press Load from stores and check the availability in the shop.
  • Manage reports unsaved matching. Save or discard the changes on the Matching tab, then change the availabilities.