Skip to content

Manual adjustments

Record ad-hoc stock changes with reason codes

Use with AI

Use with AI

Ready-made prompts Connect your AI to Pasilobus Install the CLI

This page

View as MarkdownPlain text of this page Open in ClaudeAsk about this page Open in ChatGPTAsk about this page

Ready-made prompts

Fill in the parts in angle brackets, then paste into any assistant.

Step by step on your store

Read https://help.pasilobus.com/stock-control/adjustments.md. Walk me through manual adjustments in Stock Control for my store, step by step. My theme is <theme name> and I want <what you want to happen>.

Ask your own question

Read https://help.pasilobus.com/stock-control/adjustments.md. Answer this about Stock Control on my store: <your question>.

Ask Shopify Sidekick

In your Shopify admin, ask Sidekick about Stock Control. It searches these guides.

Connect your AI to Pasilobus Beta

Our MCP server lets Claude, ChatGPT, OpenClaw and other MCP clients use your Pasilobus apps. It is in beta and open to every Pasilobus account: you sign in with it when your assistant asks. Tools that change your store are marked as changes, so your assistant asks you first.

https://cloud.pasilobus.com/mcp

In Claude Code, add it, then run /mcp to sign in:

claude mcp add --transport http pasilobus https://cloud.pasilobus.com/mcp

In Claude on the web or desktop, go to Customize › Connectors › Add custom connector and paste the address. In ChatGPT, OpenClaw or another client, add it as a custom connector (MCP) with the same address.

Install the CLI

npm install -g pasilobus

Run your apps from the terminal or a coding agent. These only read, so they are safe to try:

pasilobus stock-control health

Stock health: out of stock, reorder now, low, dead stock and inventory value

pasilobus stock-control purchase-orders

Find purchase orders by supplier, reference or status

pasilobus stock-control start-count

The link that starts a stock count, a receive or a transfer

pasilobus apps lists your apps on the store; pasilobus <app> help lists what each app can do. How it works

On this page
  1. When to Use an Adjustment
  2. Creating an Adjustment
  3. Reason Codes
  4. Viewing the Adjustments Audit
  5. Adjustment vs Count vs Direct Edit

Adjustments let you record ad-hoc stock changes with a reason code — damage, shrinkage, found inventory, data correction — without running a full count. Every adjustment is logged with who made it, when, and why.

When to Use an Adjustment

Use an adjustment when the change is small, targeted, and has a specific cause:

  • A unit was damaged in the stockroom
  • You found stock that was miscounted
  • A customer return was processed outside of Shopify
  • You need to correct a typo in on-hand without running a full count
  • Shrinkage has been confirmed after a physical check

For anything larger — reconciling a whole section of the store, counting a category after receiving a delivery — use an Inventory Count instead.

Creating an Adjustment

From the Inventory page, click any variant to open its drawer, then click Adjust.

  • Delta — the change in units (positive to add, negative to remove)
  • Location — which Shopify location the change applies to
  • Reason — pick from the reason codes (Damage, Shrinkage, Correction, Found, Return, Other)
  • Notes — optional free-text explanation

Save, and the change posts to Shopify immediately at the chosen location.

Reason Codes

Reason codes are what make adjustments useful versus just editing on-hand directly. They let you run the Adjustments Audit report and see patterns — e.g. "damage is concentrated in these three SKUs" or "this location has more shrinkage than the others."

Viewing the Adjustments Audit

Go to Reports › Adjustments Audit to see every adjustment across your account, with filters for date range, location, reason, and user. See Reports for details.

Adjustment vs Count vs Direct Edit

Three ways to change on-hand, each with a different purpose:

  • Direct edit (the on-hand field in the drawer) — fast, no reason recorded. Use for quick fixes where you don't need an audit trail.
  • Adjustment — records a reason and appears in the audit report. Use when the why matters.
  • Inventory count — full session with scanning, expected vs counted reconciliation, and a committed delta per item. Use when you're reconciling many items at once.

When in doubt, prefer an adjustment over a direct edit — the extra reason code makes future analysis much easier.

Talk to a person.

The people who build our apps answer support themselves. Send us a message or email us, and a person replies, usually within one business day. There's no chat.