Check a stock before use. Use the permitted Labguru records and show me the supporting evidence.
Once the records are shared with me, I’ll compare the lot, expiry and storage identifiers of the selected stocks with the batch or experiment record.
Selected stocks: stock ID and name, associated inventory-item ID and type, and the lot, barcode, expiry and storage fields the API returns.
Check a stock before use
- Findings linked to source records
- Missing evidence and unresolved questions
- Follow-up work for your team
1What’s connected.
Track a stock’s identity, lot and expiry alongside a Seal workflow. Select the records to share in Seal, then reference them with @ in documents, comments and Neil.
Connection setup and permissions
Seal’s Labguru connector reads selected stocks with a personal API token from a dedicated account. It does not write to Labguru.
The connector checks access to Labguru’s v1 stocks endpoint. It captures stock ID and name, the associated inventory-item ID and type, and the storage, lot, barcode, expiry and modification fields the API returns. Absent optional fields stay absent.
Quantity and concentration, linked inventory-item content, experiments, analytical results, custom fields and attachments are not included. A stock summary is not a release certificate. Labguru’s v1 API sends the token as a query parameter, so treat query strings in API access logs as sensitive.
Set up Labguru
- Generate a personal API token for a dedicated Labguru account that can see only the intended stocks. The token inherits that account’s permissions.
- Open Settings → Integrations → Labguru. Enter the HTTPS workspace root ending in labguru.com and the token, then choose Test and connect.
- Choose Stocks, browse or enter an exact numeric stock ID, select stocks and Seal groups, and enable sharing. Compare lot and expiry in the first capture with Labguru.
2Connect in Seal.
Sign in to Seal and open Settings → Integrations. An organisation admin can review the connection and complete the guided setup.
3What Neil can do with Labguru once connected
Once the connection is set up and the records are shared:
- Check a stock before use
- Compare the lot, expiry and storage identifiers of the selected stocks with the batch or experiment record.
- Trace a lot in an investigation
- Identify which Seal records reference the selected stock, its lot and its barcode.
- Flag expiring stock
- Compare expiry dates on the selected stocks with planned work and list those that expire first.
4Connection questions
Can Neil see stock quantities?
No. Quantity and concentration are outside this connector’s scope. It captures identity, lot, barcode, expiry and storage fields; compare them with Labguru after the first capture.
5Before it goes live.
Access
The organisation library reads only; it makes no changes in Labguru. Define which records are shared and which Seal groups can read them.
Data and failure handling
Agree the field mapping, identifiers, units and source of record. Test missing or duplicate data, interrupted transfers and recovery before relying on the connection.
Verification and release
Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.