TracePharma
Integrations / LSPedia

Integrations · Serialization platform

TracePharma + LSPedia

Receive EPCIS from LSPedia-connected wholesalers and manufacturers through HTTPS inbound presets—while running operator-first receiving, exceptions, and compliance on TracePharma.

Preset: lspedia HTTPS Pulse ecosystem vendor

LSPedia OneScan and Exchange serve many US trading partners. TracePharma interoperates via HTTPS webhook when partners push EPCIS to your tenant. Use it alongside—or instead of—a OneScan module for US L4 workflows you actually operate.

Inbound interoperability

  • HTTPS inbound webhook with tenant-scoped token authentication.
  • EPCIS 1.2 XML and JSON-LD capture into unified receiving.
  • 3T matching and exception surfacing before inventory acceptance.

Outbound & compliance

  • Outbound EPCIS generation for pharmacies, wholesalers, and 3PL customers.
  • Partner-specific routing and ACK monitoring per connection.
  • EPCIS 2.0 repository with queries and subscriptions for investigation.

Typical cutover steps

  1. 1 Confirm whether partners push via LSPedia Exchange or direct HTTPS.
  2. 2 Create an inbound connection with the LSPedia serialization provider preset.
  3. 3 Share your webhook URL and inbound token from Integrations.
  4. 4 Run a test file from Onboarding or Receiving before go-live.

Best for

LSPedia interoperability FAQ

Do I need LSPedia Exchange to use TracePharma?
No. TracePharma connects known partners directly. Exchange is optional on the partner side; your cutover focuses on re-pointing EPCIS delivery to TracePharma endpoints.
Is this the same as running LSPedia OneScan?
No. TracePharma is your L4 hub. LSPedia interoperability means we ingest and send EPCIS with partners already on OneScan—not that you must license OneScan modules.

Connect LSPedia in your tenant

We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.

Request a demo