Brand Protection
& L5 Compliance for MAHs

SmartHub Connect^™ is designed to make MAH compliance predictable. We standardize onboarding, validate at ingest, and issue a Validation Receipt for every submission, so your team spends less time firefighting exceptions and more time moving product.

Standards

first interoperability

Built on GS1 EPCIS. We accept EPCIS 1.2/2.0 (XML/JSON/JSON-LD) and normalize submissions into a canonical model for consistent validation and audit.

The MAH reality

Most MAHs don’t struggle because they ‘don’t have EPCIS.’ They struggle because onboarding is slow, requirements are unclear, and failures become endless remediation loops.

SmartHub Connect^TM is built to change that operating reality: clear requirements, consistent validation, actionable feedback, and shared proof.

How
MAHs connect

Canaux de production recommandés :

AS2 + API REST

Supported for transitional use:

SFTP (legacy)

Supported for onboarding/tests:

Web portal upload

We guide MAHs to the fastest viable path based on technical maturity, without turning onboarding into a blocker.

Submission Flow

What happens when you submit

Step 1: Submit EPCIS

(AS2, REST API; SFTP legacy; portal upload for onboarding/tests)

Step 2: Normalize to a canonical model for consistent downstream handling

Step 3: Validate at ingest

(Schema + business validation rules)

Step 4: Receive a Validation Receipt

(Shared with the regulator)

Step 5: Fix and resubmit with clear failure reasons and a shorter remediation cycle

Reçus de validation

Validation Receipts: proof you can use

Every submission generates a Validation Receipt that both MAH and regulator can reference. This ends ambiguity in audits, escalations, and disputes.

Each Validation Receipt includes:

Receipts can be exported with a complete audit pack (receipt + validation report + supporting logs).

Les reçus de validation confirment l'intégrité de la soumission + le résultat de la validation. Ils ne constituent pas une approbation réglementaire.

high level
What we validate at ingest

Validation is designed to prevent downstream chaos and reduce resubmission loops:

Why outcomes become predictable

SmartHub Connect^TM reduces variation by normalizing all supported formats into one canonical model and enforcing the regulator’s rules consistently.

Result: fewer surprises, fewer resubmissions, shorter time-to-validation, and a clearer operational workflow for MAH teams.

Onboarding

Onboarding: what to expect

Account + access setup

Roles, permissions, technical point of contact

Connectivity setup

AS2 or API; legacy paths if needed

Test submissions

Validate, remediate, repeat until stable

Go-live readiness

Repeatable passes, predictable correction cycles

Continuous Operations

Production submissions with ongoing dashboard visibility and receipt-backed proof

Support

How we support you

MAH
FAQs

1. Do you accept EPCIS 1.2 and 2.0?

Yes—EPCIS 1.2/2.0 in XML/JSON/JSON-LD.

2. What if our EPCIS fails validation?

You receive clear failure reasons, remediate, and resubmit. The goal is shorter correction cycles, not ticket chaos.

3. Does a Validation Receipt mean regulatory approval?

No. It confirms submission integrity and validation outcome, not regulatory approval.

4. Do you support SFTP?

SFTP is supported for legacy use and transitional flows. Recommended production channels are AS2 + REST API.

Prochaines étapes

Download

Download the MAH Onboarding Guide

Schedule

Schedule onboarding kickoff

Soumettre

Submit first test cycle

Go live

Go live with predictable, receipt-backed submissions

Brand Protection
& L5 Compliance for MAHs

first interoperability

The MAH reality