Routmoute Sirene Bundle Laravel Package

Product Decisions This Supports

What this package does: wraps the French government SIRENE company registry (INSEE) behind a PHP service, so you can look up and validate companies by SIREN/SIRET — legal name, legal form, NAF activity code, registered address, headcount band, establishment status.

• B2B signup & onboarding gates. Validate that a company exists and is active before letting it into a self-serve funnel — cuts fake/typo'd accounts and unblocks downstream KYB.
• Invoicing and billing correctness. Legal name + SIRET + VAT consistency checks before issuing an invoice. This is the highest-value, lowest-effort use case, and it is on a timer: France's e-invoicing mandate (receipt from Sept 2026, issuance from Sept 2027) makes validated SIRET data a compliance prerequisite, not a nice-to-have. Anything that de-risks that deadline is a roadmap item worth scoping now.
• CRM/data enrichment. Backfill firmographics (size band, sector, region) on existing accounts to power segmentation, lead scoring, and territory assignment — a cheap retrofit onto data you already hold.
• Build vs buy. Don't build an INSEE client in-house: auth, rate limits, schema churn, and French legal-form vocabulary are exactly the kind of surface that rots quietly. A thin wrapper is the right buy/borrow. The genuine build decision is the policy layer on top — what you do when lookup fails, when a company is "ceased," or when name matches but SIRET doesn't. Own that; don't own the transport.
• Roadmap signal from v1.1.1. The only change is an updated API_URL. That is an upstream endpoint migration, not a feature. Treat it as a reminder that this dependency can break without a semver-major, and that your integration needs a configurable base URL and an alert on lookup failure rate.

When to Consider This Package

Adopt when:

• Your market includes France and you need company identity data for onboarding, invoicing, or enrichment.
• Your stack is PHP and you want a small, single-purpose dependency rather than a full data vendor contract (e.g. Dun & Bradstreet, Pappers commercial tiers).
• Volume is moderate and you can tolerate INSEE's own rate limits and availability; lookups are not on your hot request path.
• You want to keep the option of swapping data source later behind your own interface.

Look elsewhere when:

• You need a Laravel package specifically. The name is ...-bundle — this is a Symfony bundle. In Laravel you will be adapting service-container wiring rather than installing a first-class provider. Budget a small spike to confirm fit; do not assume composer require plus a facade.
• You need data SIRENE doesn't carry: contact emails, revenue, technographics, international entities. This is registry data only.
• You need SLA-backed uptime, bulk exports, or fuzzy match/dedupe scoring at scale — that is vendor territory.
• You need real-time inline validation in a checkout flow with sub-100ms budget; cache aggressively or use a batch/queue path.

Given v1.1.1 specifically: the patch is safe to take — it is a URL constant, no API or data-shape change. Verify your configured base URL or env override still resolves against the new endpoint, run one smoke lookup per environment, and confirm error handling degrades gracefully (a failed lookup should not hard-block a paying customer's invoice).

How to Pitch It (Stakeholders)

For executives: This is a small, free dependency that gives us authoritative French company data — official name, SIRET, legal form, sector, size, address — straight from the government registry. It supports three things we care about: cleaner B2B signups, correct invoicing, and readiness for France's 2026 e-invoicing mandate. Cost is a few days of engineering, not a vendor contract.

For engineering: Single-purpose INSEE/SIRENE client, thinly maintained, patch-level release cadence. The v1.1.1 release is an endpoint URL update — take it, but it's a tell: this dependency can change behaviour without a major version bump. Wrap it behind our own CompanyRegistry interface, make the base URL configurable, cache lookups, and alert on failure rate so an upstream migration never surfaces as a customer-facing outage. Note it ships as a Symfony bundle — confirm the Laravel integration path before committing to a timeline.

The ask: one spike to validate integration and error-handling behaviour, then a scoped slice on the invoicing validation path — the highest-value, most deadline-driven use case.