I built a browser extension that checks device identifiers and accessory lots against order quantities before allowing label creation in the supported fulfillment workflow.
Warehouse staff needed to catch missing identifiers, duplicate device serials, and quantity mismatches without leaving their existing shipping interface.
The extension combines scanner input and native product verification with order-scoped state and shared serial claims. After explicit verification, it writes a Cloudflare record URL into ShipStation Custom Field 1.
- 01Scanner input
- 02Verify and commit
- 03Record URL
This overview shows the concerns involved; the account below distinguishes delivered work from plans.
Integrating with a third-party interface avoided replacing the warehouse workflow, but introduced DOM changes and network availability as ongoing maintenance concerns.
Devices and accessories need different checks
Device serials must be unique. Accessories can share a lot number, so repeated lots are accepted only within the ordered quantity. The checks reconcile the captures with the order before the supported label action is enabled.
Drafts are not committed records
The deployed workflow stores the Cloudflare URL after verification, rather than filling the field with raw draft scans. QA material covers tab isolation, resets, offline retries, and interrupted verification; the test matrix alone is not proof that every scenario passed.
Scope of the controls
These are controls within the supported browser workflow, not a claim of regulatory certification or protection across every fulfillment channel. The extension is launched; its proposed warehouse replacement still awaits approval.