How Vision Scan fits your compliance and ERP ecosystem
Vision Scan is the receiving-intelligence layer that keeps every traceability field connected to the correct product identity. It feeds the compliance and inventory systems you already run — it does not replace them.
Vision Scan is not initially a full DSCSA network platform
Vision Scan does not issue serial numbers, originate or broker EPCIS events, or operate a trading-partner exchange network. Those functions stay with your serialization provider, your compliance network and your trading partners. Vision Scan qualifies the product identity at the moment of receiving and hands clean, canonical data to those systems.
- Serialization issuance and packaging-line aggregation
- EPCIS event origination and brokerage
- Trading-partner network exchange and onboarding
- Regulatory submission or compliance reporting of record
What Vision Scan owns
- GTIN-first pharmaceutical package identity at receive time
- Association of lot, expiration and serial to the qualified GTIN
- Purchase-order and product qualification against the receiving system of record
- Review-required exception rescue instead of silent auto-correction
- Canonical, versioned receiving payloads for downstream systems
What your partners own
- Serialization issuance and packaging-line systems
- EPCIS repositories and event brokerage
- VRS responder infrastructure operated by manufacturers
- Authorized Trading Partner credential authorities
- ERP and WMS systems of record
The terms, defined
- EPCIS — Electronic Product Code Information Services
A GS1 standard for sharing supply-chain event data — what happened, to which product identifier, where, when and why. Trading partners exchange EPCIS events to build a traceability history for a product.
Vision Scan produces the qualified receive data that an EPCIS repository or broker can turn into a receiving event. Vision Scan is not itself an EPCIS repository.
- VRS — Verification Router Service
A routing service that forwards a product-identifier verification request to the manufacturer responsible for that identifier, so the requester can confirm the identifier is legitimate. It is most commonly used for saleable-returns verification.
Vision Scan assembles the identifier fields (GTIN, serial, lot, expiration) that a VRS request requires. Routing and the manufacturer response remain with the VRS provider.
- ATP — Authorized Trading Partner
A supply-chain participant that holds the licensing or registration status required to trade prescription product. ATP credentialing lets systems confirm that the party on the other side of an exchange is authorized.
Vision Scan records which enrolled site and device produced a receiving session. It does not issue, validate or vouch for ATP credentials.
- ERP / WMS — Enterprise Resource Planning / Warehouse Management System
ERP is the system of record for purchasing, inventory valuation and finance. WMS governs warehouse execution such as putaway, replenishment and picking. Both hold the authoritative inventory position Vision Scan posts against.
Vision Scan qualifies receipts against purchase orders and returns canonical receiving data for the ERP or WMS to post. It does not replace either system.
- GTIN — Global Trade Item Number
The GS1 product identifier carried on pharmaceutical packaging. It identifies the trade item, distinct from the lot, expiration and serial values that qualify a specific package.
The GTIN is Vision Scan's primary resolution key: identity is qualified first, then dependent traceability fields are associated to it.
Product and GTIN master-data synchronization
Receiving intelligence is only as good as the product master behind it. Vision Scan synchronizes the product and GTIN master data it resolves against, so a scan that qualifies an identity is checked against the catalogue your systems agree on.
- released
GTIN and product catalogue synchronization
Import and refresh the product/GTIN catalogue Vision Scan resolves receiving scans against, including NDC-to-GTIN relationships used in pharmaceutical receiving.
- released
Purchase-order reference synchronization
Qualify receipts against open purchase-order references so a scanned item can be matched to what was actually ordered.
- preview
Unknown-GTIN review queue
Route identifiers absent from the synchronized catalogue into a review queue rather than accepting or discarding them silently.
- roadmap
Bidirectional master-data write-back
Planned direction for proposing catalogue corrections discovered during receiving back to the upstream product master.
Connectors and integration boundaries
- Released Live in the current product and demonstrable today.
- Partner Delivered together with a named integration partner and enabled per customer onboarding.
- Preview Available for evaluation or beta, not generally available. Never presented as released.
- Roadmap Planned direction only. Never presented as available.
Released
- Released
Canonical receiving payload
Versioned canonical JSON for a completed receiving session, consumable by any downstream receiving API.
Boundary: Vision Scan emits the payload; posting and reconciliation stay with the receiving system.
- Released
Product / GTIN master-data synchronization
Keep the product and GTIN catalogue Vision Scan resolves against synchronized with your product master.
Boundary: The upstream product master remains authoritative.
Partner
- Partner
ERP / WMS receiving integration
Post qualified receipts into an ERP or WMS receiving endpoint, scoped per customer's system and validated during onboarding.
Boundary: Integration is validated per named ERP/WMS and API version; Vision Scan publishes no blanket compatibility claim.
- Partner
VRS verification request assembly
Assemble the identifier fields a VRS verification request requires and hand them to a partner VRS provider.
Boundary: Routing and manufacturer response are the VRS provider's responsibility.
Preview
- Preview
EPCIS receiving-event handoff
Preview capability to shape qualified receive data into an EPCIS-compatible receiving event for a repository or broker to publish.
Boundary: Vision Scan does not originate, broker or store EPCIS events of record.
Roadmap
- Roadmap
Authorized Trading Partner credential exchange
Planned direction for carrying ATP credential context alongside receiving data.
Boundary: Vision Scan does not issue or validate ATP credentials.
- Roadmap
Exception and recall handoff
Planned direction for routing receiving exceptions and recall matches into your exception-management process.
Boundary: Recall determination and regulatory action remain with your compliance function.
Talk to us about a connector or partnership
Tell us which ERP, WMS, EPCIS repository, VRS provider or serialization partner you run, and we will walk through where Vision Scan fits and what a connector conversation looks like.