Enterprise DNA

Instead of LabCup

Stop renting LabCup. Own your chemical inventory system.

We build your version around your laboratories, map your authorised LabCup export and run the system for you. Your inventory owners keep control of the records and their review process.

LabCup does not show a public subscription price on the product page reviewed. Bring your current quote and we will compare the work your laboratories need.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What your LabCup agreement covers

Separate the inventory record from the wider laboratory platform

LabCup combines chemical records with services and interfaces around them. Compare the parts your team uses before choosing the scope of your own version.

science

Chemical container tracking

LabCup tracks individual chemical containers with identifying labels. The free version keeps each container, quantity and location together.

description

Safety data sheet sourcing

LabCup describes automatic sourcing and updates for many suppliers. We scope your document connections around the sources your reviewers approve.

groups

Shared laboratory visibility

LabCup supports sharing chemical information across groups. We build shared access around the people responsible for your sites.

recycling

Waste oversight

LabCup exposes expired items and material marked for disposal. Your version keeps waste in the recorded onsite quantity until collection is logged.

fact_check

Compliance reporting

LabCup lists several chemical reporting features. Your version starts with selected inventory record checks and your reviewers define the wider requirements.

history

Change history

LabCup records changes to inventory items. Your version records before and after values, the operator name and the evidence for each stock movement.

Your owned version

The stocktake, the waste review and the evidence behind both

Physical stock

Know which shelves need a count

Find the containers whose recorded balance needs checking.

  • check Keep a stable identity for each container
  • check Read its current location and responsible owner
  • check Find missing and overdue physical counts
  • check Record a discrepancy with the observed quantity and its evidence

Expiry and waste

Keep expired stock and waste visible

Prepare the review before stock quietly disappears from the record.

  • check Find expired material that still has a recorded balance
  • check Look ahead to the next month of expiry dates
  • check Separate material marked as waste from usable stock
  • check Keep waste onsite until collection is recorded with evidence

Site inventory

Do not mistake current stock for the site maximum

Review the declared maximum likely at the workplace independently of today's balance.

  • check Record the basis and reviewer for each declared maximum
  • check Flag a missing declaration or a quantity above it
  • check Keep different units separate
  • check Show missing safety references and emergency access reviews beside the inventory

Follow-up

Connect the finding to the person doing the work

Keep record gaps, assigned actions and closure evidence together.

  • check Assign inventory follow-up to a named owner
  • check See overdue actions beside overdue physical counts
  • check Read the original fields from an imported record
  • check Add your own questions across movements, declarations and completed reviews

Make it yours

Design your own LabCup replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from LabCup. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your LabCup replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your LabCup data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Chemical Inventory for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Chemical Inventory for Claude Code

Connected to your own database

Which chemical inventory work needs attention now?

DEMO-NORTH

Record
ACT-01
Owner
Mere
Reason
overdue action

DEMO-NORTH

Record
N-001
Owner
Mere
Reason
expired stock

DEMO-NORTH

Record
N-001
Owner
Mere
Reason
stocktake overdue

DEMO-NORTH

Record
N-W01
Owner
Ari
Reason
waste awaiting collection

DEMO-SOUTH

Record
S-001
Owner
Ari
Reason
stocktake overdue

Ask it anything

Ten questions your owned system answers

These questions run against the fictional demonstration records. They demonstrate this version without claiming that LabCup cannot answer them.

chat_bubble Which containers are overdue for a physical count?
chat_bubble Which expired containers still have stock?
chat_bubble How much material on site is already marked as waste?
chat_bubble Where does recorded stock exceed the declared site maximum?
chat_bubble Which substances have no reviewed safety-sheet reference?
chat_bubble Which site has no recorded emergency inventory access arrangement?
chat_bubble Who has the most outstanding inventory work?
chat_bubble What changed when a container moved between rooms?
chat_bubble Who closed a follow-up, and what evidence did they record?
chat_bubble What did the original imported record say?

Switching

How to switch from LabCup

A move usually involves exporting your inventory, mapping your records and rules, checking the imported data, and running both systems side by side before you retire LabCup.

  1. 1

    Export your inventory

    Request an authorised export of the inventory and container records you need, including the available quantities, locations, expiry details and waste records. LabCup says data can be exported, subject to institutional restrictions. Ask LabCup which fields your account can export and whether the export is CSV or XLSX. Treat attachments, historic movements and access rules as separate migration questions.

  2. 2

    Map and test the records

    Match the headings in your LabCup export to the fields in the new inventory. Start with a test import that checks the mapping without saving records. The import preserves original columns, reconciles unchanged repeats and does not overwrite changed duplicates. Resolve mapping questions before loading the full export, and do not expect the import to fill in missing hazard classifications.

  3. 3

    Review the import issues

    Check what the test import identifies before you proceed. Investigate invalid records, headings that need mapping and any repeated records that have changed, then compare the results with your source export. Check that quantities and locations make sense. The import rolls back an invalid batch, so resolve the reported issues and run the test again rather than relying on a partial load.

  4. 4

    Run both systems briefly

    Keep LabCup available while you begin using the new inventory for a short period. Compare records and physical counts, and check that the new process captures the changes your team needs to record. Use this period to surface gaps in your field mapping or local rules. Confirm that the people responsible for inventory review can work with the new process before you retire LabCup.

  5. 5

    Retire LabCup

    Switch off LabCup only after you have checked the imported records and agreed that the new process covers your requirements. Confirm separately what you need to do about attachments, historic movements and access rules, since these require their own migration scope. If you rely on LabCup features beyond the replacement's inventory scope, compare those requirements before retiring the system.

construction

Where the real effort goes

The main work is usually mapping your LabCup headings to the new fields, reconciling quantities, and setting your own fields and review rules. You also need to decide how much history to bring across. Attachments, historic movements and access rules need separate migration scope. If Enterprise DNA runs the setup, they map your records and build your workflow as part of that work.

Not ready for a call?

Get your LabCup switch plan by email

We will send you the step-by-step plan for moving your business off LabCup, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor and ask for the weekly inventory review
  3. 3 Map your authorised LabCup CSV or XLSX export, run import with --dry-run, then reconcile before saving
  4. 4 Review the safety references, site maxima and access arrangements before using real records
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your sites, container fields and review rules
  • check Your authorised LabCup data mapped and reconciled
  • check Shared screens, mobile capture and document connections scoped around your team
  • check Your preferred hosting and database, with access and backup arrangements
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with agreed access, backups and recovery checks
  • check Stocktake and expiry reviews prepared for the inventory owner
  • check Kept working as sites, staff and procedures change
  • check Operated through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute inventory review

Questions

Instead of LabCup, answered

Is this a complete replacement for every LabCup feature? expand_more

The free version handles container records, quantity changes, stocktake, expiry, waste and selected inventory checks. Enterprise DNA scopes shared screens, mobile scanning, document sourcing and wider reporting around your laboratories. Compare those requirements before retiring the current system.

Can we bring our LabCup records across? expand_more

Yes, from an authorised inventory export. LabCup says data can be exported, subject to institutional restrictions. We map the actual headings, reconcile quantities and preserve the original values. Attachments, historic movements and access rules need their own migration scope.

Does a clear record check mean the laboratory is compliant? expand_more

No. The checks identify missing or overdue information against selected New Zealand inventory guidance and local review policies. Your competent reviewer confirms applicability, chemical classifications, storage requirements and access to current safety information. Australian sites need their local rules mapped.

What happens to stock marked for disposal? expand_more

It remains in the recorded onsite quantity as waste. Collection is recorded separately with evidence. The handover is a working draft for review with your collection provider, not a transport approval or disposal instruction.

What does Enterprise DNA charge? expand_more

One setup fee, then a retainer. Sam scopes your export, sites, review process and connections before proposing your version. LabCup does not show a public subscription amount on the product page reviewed, so we compare against your own agreement.

Bring your LabCup agreement and one inventory export

Book 30 minutes with Sam. Walk through your stocktake, expiry and waste review, then agree what your own version needs and who keeps it running.

Book 30 minutes with Sam Get the free version

Chemical Inventory for Claude Code is free and open source, published by Enterprise DNA.

Done paying for LabCup?

Get your version built