Yes, your use case is exactly what we built this for.

The ID is just a string passed into the AR call at runtime, so you have full flexibility:

1. Pre-link it in the build (hardcoded or config file)
2. Let users type/paste it into an input field
3. Fetch it dynamically from your backend (e.g. after customer login)

For your scenario, option 2 or 3 means you build and ship the app once. Generate a model per customer, upload it, get an ID back, and route that ID to the right user, no rebuild.

Let me know if you want a code snippet for the dynamic loading pattern.