Downloading the EU and Australia labels and IFU together made it clear that neither market's requirements could be assumed to match the other's, even for the same product and classification.
Two markets downloaded together, still two requirements
Handling the EU and Australia labels in the same pass is a scheduling convenience. It doesn't mean the two markets share the same specific requirement, and treating them as identical is exactly where the assumption breaks.
- Comparing each IFU/label section against the master content and the destination country's regulatory requirements
- Tracking every open item (missing translation, missing symbol, outdated claim) through to closure
- Confirming the EU and Australia versions independently before closing either
What the shared assumption risks
A country-specific IFU/label shipping with content that doesn't match the current master, an outdated warning, a missing symbol, a wrong classification, is what happens when one market's requirement is assumed to cover the other.
What the delivery confirmed
Delivering the Australia/EU labeling requirements and labels closed an open item in the device's international registration file, with each market's requirement verified on its own terms.
The Real Takeaway
Country-specific label requirements can't be assumed to match a neighboring market's rules.
Even when the product and classification are identical, the requirement itself can still differ.