Side-effects catalogue

What happens automatically when you do something in Logistified. A reverse index, useful when you’re debugging “why did this update?” or “why didn’t this happen?”

Purchase order actions

You send a PO (Draft → Sent)

The PO PDF is generated.
An email goes to the supplier (with PDF attached).
The PO status moves to Sent.
A log entry records the change.
The supplier-side incoming inventory remains unchanged.

You confirm a PO line (line moves from ordered to confirmed)

Shopify’s incoming inventory for that variant + location goes up by the confirmed quantity.
If all lines confirmed, the PO moves to Confirmed.
A log entry records the change.

You receive a PO line

Shopify’s on-hand for that variant + location goes up by the received quantity.
Shopify’s incoming for that variant + location goes down as received quantity is successfully synced to on-hand stock. If only part of an over-receipt syncs, the unsynced remainder stays in the PO incoming ledger for the next retry.
A log entry records the change.

You cancel a PO

The PO status moves to Cancelled.
Any pending incoming for this PO’s lines is rolled back in Shopify.
The PO is archived (soft-deleted).
A log entry records the change.
Credits applied to this PO are NOT automatically reversed.

Transfer order actions

You ship a TO (Draft → Sent)

Source location’s on-hand decreases.
Destination location’s incoming increases.
Both pushed to Shopify.
A log entry records the change.

You receive a TO line

Destination location’s incoming → on-hand.
Pushed to Shopify.
A log entry records the change.

Stock take actions

You complete a stock take

For each line, Shopify’s on-hand is set to the counted quantity.
The stock take’s completion date is stamped.
A log entry records the change.

RMA actions

You issue a supplier credit (single line)

A credit row is created in the supplier’s pool.
The credit memo number is auto-generated.
The line’s credit status flips to “Issued.”
Note: the RMA header’s total credit amount does NOT auto-recompute. Use bulk or grouped credit issuance to trigger the recompute.

You issue a grouped credit

A credit row is created.
Every line on the RMA flips to “Issued.”
The RMA header’s total credit amount recomputes.

Supplier credit actions

You apply a credit to a PO

An application record is created.
The PO’s total due decreases.
The credit’s available balance decreases.

Cloud Platform actions

You revoke a Cloud Platform session

The session is marked revoked.
Within ~30 seconds, devices using the link are rejected.

Plan changes

You upgrade your plan

Newly-unlocked features become accessible immediately.

You downgrade your plan

Newly-locked features paywall immediately.
Your data is preserved.
Some scheduled jobs may run once more before falling silent.

Things that don’t happen automatically

This is the list of common surprises, actions you’d reasonably expect to be automatic but aren’t.

Cancelling a PO does not reverse applied credits.
Cancelling a TO does not reverse received quantities at the destination.
Cancelling an RMA does not void issued credits.
The “Marked as paid” toggle does not validate against payments.
A delete in Logistified (via Data Exclusion) does not delete in Shopify.
A re-sync does not delete stale rows; it adds and updates only.