Find the right troubleshooting guide
Start with the workflow where the problem appeared. An unavailable number, an unfinished action and a completed action with a pending follow-up need different responses.
If a save or submit timed out, reopen the original record and check its status and history before starting over. A missing confirmation does not prove that nothing happened.
Choose the symptom
| What you see | First check | Guide |
|---|---|---|
| Workspace preparation is running, stalled or needs attention | Open preparation details from Home and inspect the current run. | Preparation and sync problems |
| A quantity is blank, unknown or unavailable | Confirm the material and location, then refresh the underlying view. Do not enter zero to clear the message. | Stock quantities |
| Zapstra Inventory Management stock changed but Shopify did not | Check inventory authority, whether that stock is set to sync, and the workspace's live-sync state. | Inventory authority and syncing |
| Stores show different stock for the same physical location | Check material matching and shared-pool membership before changing quantities. | Locations and stock pools |
| An order-plan row cannot be applied | Inspect its material, source, destination, currency and quantity warnings in the proposal. | Review and apply a plan |
| A spreadsheet import has errors or changed data | Open its run, read the row results and use the correction or revalidation action offered. | Data Exchange |
| A PO cannot be sent | Check its destination address, line currency and required-by date; inspect any warning requiring acknowledgement. | Send and manage orders |
| A supplier has proposed different quantities, prices or dates | Review the proposed version before accepting or revising the order. | Supplier changes |
| A shipment is marked shipped or delivered, but stock has not increased | Check whether a receipt was completed for the goods that actually arrived. | Receive stock |
| Goods were damaged, short or incorrect | Record the actual receiving outcome and inspect the resulting dispute; send the chosen resolution when ready. | Disputes and replacements |
| An invoice cannot be approved | Compare its currency and charges with the PO and inspect the reason displayed. | Invoices and credits |
| A transfer cannot be approved, picked or received | Confirm which stage is blocked and open the request or task with the refusal. | Transfer requests and transfer execution |
| Production released successfully but did not start | Reopen the production order. Released stock can remain committed while Start needs attention. | Production planning |
| A build is applying or its result is uncertain | Check the original order before attempting another completion or stock adjustment. | Production execution |
| A scanner has pending or rejected work | Check the captured work and its confirmed outcome before repeating it on desktop. | Stock Scan recovery |
| An action says allowance, capacity or billing information is unavailable | Open Billing and inspect the actual state and original approval attempt. | Plans and capacity |
| An expected button is missing or disabled | Check the record's state, organization/app access and the reason shown beside the action. | Users and permissions |
Check the right record
Before comparing two results, confirm all of the following:
- You opened Zapstra Inventory Management in the intended Shopify store and organization.
- You selected the same material and receiving or source location.
- The quantities use the same unit. Three cases of 24 each means 72 each.
- The money values use the same currency and price basis.
- You are comparing the same milestone. A saved draft, recorded shipment, completed receipt and paid invoice each describe different work.
For example, a supplier can report a shipment of 72 each while the warehouse has received only 48 each. The remaining 24 each are still due; recording the whole 72 as received would misstate stock.
See the glossary and status reference for the terms used in these comparisons.
When a retry is appropriate
Refresh and review are useful when a screen could not read current information. Repeating a stock change or sending another order requires more care.
If the original action is still running, continue to follow that record. If it succeeded but a follow-up failed, complete the follow-up. If the screen confirms a refusal, correct the stated cause and retry the original workflow. When the application offers a specific retry for the same submission, use that path instead of creating a second record.
If the outcome remains unclear, open a support ticket with the record reference, approximate time, action and message shown. This is especially useful when two systems disagree or an action may already have affected stock.