Reference · built on requestOperator by FibricInventory & supply

Shrinkage Watch

Correlates unexplained negative adjustments with door events, voids, and shift times, and proposes a recount or review when loss clusters.

Request accessPricing ↗

About

Shrink hides inside ordinary records: a negative adjustment with a blank memo, a void just before close, a stockroom door opened outside its schedule. Shrinkage Watch reads inventory adjustments and their stated reasons, voided and refunded sales from the point of sale, access events on stockroom doors, and who was on shift at the time.

It picks out adjustments with no stated cause and groups them by item, location, hour, and shift. When losses cluster around the same door, shift, or register beyond your threshold, it proposes a recount of the affected items and a review with the timeline attached. A loss-prevention or store manager approves both.

This is a reference listing. It documents what Fibric would read from Shrinkage Watch and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • NetSuite inventory adjustments with Adjust Qty By, Memo, Location, and Bin Numbers, and Business Central item journal lines with reason codes
  • Square inventory changes moving units from IN_STOCK to WASTE or NONE, and physical counts, through BatchRetrieveInventoryChanges
  • Square refund.created and order.updated events, for voids and refunds by location and time
  • Stockroom door events: Brivo access events with securityAction, actor, and occurred, or Verkada door_opened, door_held_open, and door_forced_open
  • Rosters and timesheets from Deputy or 7shifts, to place each event on a shift
  • Cycle counts already scheduled or completed, so a recount is not proposed twice

Proposed actions

  • Target capability: propose a recount of the affected items and bins, as a NetSuite inventory count or a Business Central physical inventory journal batch
  • Target capability: propose a review case with the adjustments, door events, voids, and shift roster laid on one timeline
  • Target capability: propose a reason for an adjustment that has none, for the manager to confirm or replace
  • Target capability: propose a tighter door schedule or a suspended credential to your access-control administrator

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Find the stockroom hour where units go missing

    NetSuite negative adjustments with a blank Memo are grouped by hour and matched to Brivo door events and Deputy shifts. A recount and a review are proposed when one hour keeps recurring.

    With NetSuite, Brivo Access, Deputy

  • Catch a register with too many voids

    Square refunds and canceled orders per location are set against WASTE and NONE inventory changes in the same hours. A review is proposed with the 7shifts roster for those hours attached.

    With Square, 7shifts

  • Recount after a forced door

    A Verkada door_forced_open on a stockroom is followed by Business Central negative adjustments for items kept there. A physical inventory journal for that bin is proposed to the store manager.

    With Verkada, Microsoft Dynamics 365 Business Central

Requirements

  • Inventory adjustments with a memo or reason field, from NetSuite, Business Central, or Square
  • Door events from an access-control platform: Brivo, Verkada, or Kisi
  • Shifts or timesheets from Deputy or 7shifts covering the locations watched
  • A loss-prevention or store manager named to approve recounts and reviews
Authentication
ERP credentials with adjustment and count read permissions, a Square access token with INVENTORY_READ and order and refund read scopes, an access-control API credential with event read, and a scheduling API token.

Limits

  • It correlates. It does not name anyone as responsible. A review shows who was on shift and who used the door; the conclusion is yours.
  • Brivo access event queries cover at most 24 hours per call, with times truncated to the hour. Timelines are stitched from daily reads.
  • An adjustment with a reason you list as expected is excluded. If everyone leaves the reason blank, everything looks unexplained.
  • Video is not read. A Verkada or Brivo event carries the door and the credential, not footage.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Shrinkage Watch ↗

Questions and answers

What counts as unexplained?
A negative adjustment whose memo or reason code is blank or matches none of the reasons you list as expected, such as damage, sample, or count correction. Square changes to WASTE or NONE without a physical count are included. You set the list.
What does the manager approve?
A recount for named items and bins, and a review case with a timeline: each adjustment, the door events around it, voids and refunds at that location, and who was on shift. Each can be approved, edited, or declined on its own.
Does it ever change access, suspend a credential, or post an adjustment?
No. Access changes are proposed to your administrator and made by them. Adjustments are never posted; a recount is proposed instead. Every proposal and decision is recorded with its evidence, the approver, and the time.
Ask about Shrinkage Watch

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy