Apple Business: govern locations at scale without losing control
Apple has added bulk location creation and editing to Apple Business. A verified organization can process up to 10,000 rows per file, then track validation and correct errors from the Activity Center. For a multi-site network, the gain lies as much in data governance as in import speed.
1. What Apple added
The October 8, 2026 Apple Business release notes announce the ability to add and edit multiple locations. To create place cards in bulk, the organization must be verified, have a brand, and assign the operation to a permitted role. Apple accepts CSV, TSV, or XLSX files with no more than 10,000 rows.
Bulk editing requires at least five locations. The export can be filtered; without a filter, it contains every location in the organization. After upload, Apple shows a change summary and submits the information for review.
2. The file is a production change
Templates contain required, optional, and conditional fields. They rely on brand identifiers, reference lists, and formatting rules. An invalid row can prevent location creation; a warning can leave a place card published with information that must be corrected manually.
Hours can be entered as free text, but Apple must be able to interpret them. Postal codes beginning with zero, common in France, require special care in spreadsheets to preserve the initial zero. Multilingual content also uses syntax defined by Apple.
3. What does this change for a Belgian or French organization?
A retailer, bank, healthcare network, or public body can now align its points of presence rapidly across Apple Maps and Apple services. In Belgium, teams should organize language variants and responsibilities between headquarters and local sites. In France, large networks can segment imports by region, brand, or wave to limit the blast radius of an error.
The feature does not replace Apple Business Manager and does not change MDM enrollment. Apple Business manages brand presence and customer-visible locations here; Apple Business Manager remains the foundation for assigning devices, accounts, and apps. Roles and procedures should make this separation explicit.
4. Underside analysis: establish a controlled data pipeline
Our view is that a 10,000-row spreadsheet should be treated as a production batch: identified source of truth, business owner, peer review, and change log. The downloaded file, corrected version, and Apple report should be retained together to reconstruct who changed what.
This governance complements partner access management in Apple Business and Activity Center traceability. Permissions should follow least privilege: producing, approving, and submitting the data should not depend on one person when the scope is critical.
5. Recommended operating plan
- Nominate a source of truth for addresses, hours, statuses, and languages, then freeze the batch scope.
- Download a current template and its reference files; do not blindly reuse an old structure.
- Test five to ten representative locations before a national or multi-brand wave.
- Check brand identifiers, encoding, leading zeros, languages, delimiters, and allowed values.
- Peer-review the summary before submission, then archive the submitted file and error report.
- Verify published place cards in Apple Maps and resolve every remaining warning.
Objective: industrialize multi-site updates while retaining evidence of the source, approval, and published outcome.
Define your Apple Business governanceOfficial sources: Apple Business release notes and Add multiple locations in Apple Business, reviewed and analyzed October 11, 2026.