KRAKENRX

One system for the 3PL, the virtual manufacturer, and the virtual distributor.

KrakenRX runs the warehouse floor and the commercial side of pharma fulfillment on one platform. Each company keeps its own database. Orders flow one way, shipments and inventory flow back, and every step lands in an audit trail you can defend.

Three kinds of company, one platform

Which seat are you in?

A 3PL owns the building and the physical record. A virtual manufacturer or virtual distributor owns the product, the buyers and the books. KrakenRX gives each its own tenant and wires them together.

You run a pharma 3PL

Receive, store, pick, verify, pack and ship for many manufacturers, each walled off from the next, with FEFO enforced and every action audited.

For 3PLs →

You are a virtual manufacturer

You own the product and the demand but not a building. Keep your catalog, buyers, pricing and books in your own tenant while your 3PL ships from theirs.

For manufacturers →

You are a virtual distributor

You own the buyers and the inventory you resell. Sell through a branded storefront, let the warehouse fulfill, and watch every lot move in real time.

For distributors →
How the data flows

Every record has exactly one owner. Commands go one way, events come back.

The manufacturer or distributor owns the product master, the buyers, the prices and the storefront. The 3PL owns everything physical: receipts, lots, bins, picks, shipments and returns. No record is writable in two places, so there is no merge, no conflict queue and no “which copy is right”.

When a buyer checks out on the storefront, the order is pushed into the 3PL through the same path the warehouse staff use, so it gets their FEFO allocation, license check and audit trail. As the warehouse picks, verifies, packs and ships, status, tracking and lot-level availability stream back to the owner’s tenant.

Each tenant keeps its own database. The manufacturer’s pricing and buyer list are never visible to the 3PL’s administrators, and one 3PL’s data never shares a database with another’s.

Commercial tenant

Virtual manufacturers & distributors

  • Own the product master and what is sellable
  • Own buyers, pricing and the branded storefront
  • Place purchase orders with contract manufacturers
  • Keep their own books, invoices and audit log
Physical tenant

The 3PL warehouse

  • Receives against inbound notices, lot by lot
  • Allocates FEFO at wave release, picks, verifies, packs
  • Buys labels, ships, handles returns and relabeling
  • Holds stock for many manufacturers in one building
Downstream

Pharmacies & buyers

  • Apply once with state licenses, DEA and W-9
  • Order from a storefront that shows real availability
  • Track shipments and reorder from order history
  • Start a return from the QR on the packing slip
Everywhere the warehouse is

On the floor, on the wall, on your wrist, in your car, in your terminal.

The same live truth about outbound work reaches every screen you own, and only the amount of it that screen should show.

Mobile app on the floor

Receiving, FEFO picking, blind verification, packing with live carrier rates, returns, relabeling and stock moves. Queues work offline and syncs when the network returns.

Learn more →

Apple Watch and iPhone widget

Orders waiting to pick, awaiting verification, awaiting packing and packages shipped today. On your wrist, your home screen, StandBy and the CarPlay dashboard.

Learn more →

Android TV wall board

The same four numbers on a screen bolted to the warehouse wall. Pairs with a four-digit code, turns amber then red as work ages, and shows nothing a visitor should not see.

Learn more →

Claude, connected to your data

A built-in MCP server lets Claude Desktop or Claude Code answer questions about inventory, orders, receipts and returns. Read-only, scoped to your tenant by the token.

Learn more →
Operational proof

Built for the work, not retrofitted.

FEFO allocation, enforced

The soonest-to-expire lot ships first, decided when the wave is released. Expired, held and quarantined stock is never allocated. An override needs a reason code.

Immutable audit trail

Every receive, allocate, pick, verify, pack, ship, adjust and return is written once with who, what, when, before and after. Corrections are new records that point at the old one.

A database per tenant

One 3PL's data never shares a database with another's. Inside a 3PL, each manufacturer's stock is fenced off, down to a rule that stops two owners sharing a bin.

License gate on every move

An expired blocking license on a partner or a warehouse stops orders, shipping and receiving. Buyers see no prices until their application is approved.

Lot-level traceability

Every unit carries its lot and expiry from receipt to shipment. Relabel and ownership transfers write paired ledger entries, so provenance traces back through every hop.

An invoice per shipment

Each shipment raises its own invoice with terms and a due date. Returns raise credit memos. A double-entry ledger sits underneath so the books reconcile.

Bring your own Claude

Ask your warehouse a question.

KrakenRX ships a Model Context Protocol server inside the API. Create a personal access token, add one line to Claude Desktop or Claude Code, and ask about stock by lot, order status, open receipts, returns, partners and ops health in plain language.

Read-only, and scoped by the token. Claude can tell you what is true. People change it.

Claude Code
claude mcp add --transport http krakenrx https://<your-api-host>/mcp \
  --header "Authorization: Bearer <your-personal-access-token>"
Compliance posture

Compliance-ready for pharma logistics, and honest about what that means.

Immutable audit trail, FEFO allocation, tenant isolation, license gating and lot-level traceability are built in and enforced in the database, not promised in a policy. KrakenRX is not an FDA-regulated medical device. If your scope grows into controlled substances or formal validation, we plan that with you.

Talk to an expert