If you already embed our editors inside your own website or application, you can now do the same thing with Multipart products – not just standard MegaEdit products.
In other words:
wherever you were previously able to open MegaEdit inside an iFrame, you can now open Multipart Editor there too, let users configure their parts, and then send those jobs back into your normal Infigo ordering flow.
What’s changed?
Previously, iFrame embedding was focused on our MegaEdit editor. Multipart products still had to be handled using the standard storefront journey.
We’ve now:
-
Enabled Multipart Editor to work inside embedded editors (iFrames) in the same way MegaEdit does.
-
Ensured that key editor events (such as the item being added to the basket) still flow back to your site, so your existing integration logic can continue to work.
-
Connected this to the normal Infigo order flow, so jobs created in the embedded Multipart Editor can still be added to basket, edited and ordered as usual.
From your perspective, the main difference is:
Wherever you previously said “open this product in the embedded editor”, you can now do that with Multipart products as well.
How you use it
If you’ve already embedded our editors somewhere else (for example, inside your own portal or web app), you don’t need a brand-new approach for Multipart.
You simply:
-
Configure a product as Multipart in Infigo, the same way you normally do.
-
Use your existing embedded-editor setup (iFrame) to launch that product in the editor.
-
Let the user upload/configure all parts, then:
All of the usual editor behaviour still applies – you’re just getting it for Multipart products as well now.
Follow the same embedding guide as before
The good news: you do not need to learn a new embedding method.
You (or your developers) can follow the same steps that are already documented for embedding our editors:
👉 https://academy.infigo.net/p/1784/embedding-our-editors-in-another-site
Anywhere that guide talks about embedding MegaEdit, you can now treat Multipart products in the same way:
-
same general iFrame approach
-
same idea of starting the editor from a link
-
same pattern for reacting when the editor tells your page that something has been added to the basket or finished.
How embedding our editors works (in simple steps)
At a high level, embedding MegaEdit, Multipart or Infigo Editor into your own site always follows the same pattern:
-
Get your API token
-
Make sure your domain is set up correctly
-
Because of browser privacy rules (especially Safari), your Infigo storefront needs a matching subdomain + SSL for the site that’s hosting the iFrame.
-
Example: if your portal is portal.yourdomain.com, we’ll set up something like print.yourdomain.com for Infigo.
-
This part is handled together with Infigo Support.
-
Tell Infigo which customer and product to use
-
Decide what “customer identity” you want to use in Infigo:
-
Make sure that customer exists in Infigo and is Registered.
-
Decide which Infigo product should open in the editor (this can be a standard, MegaEdit or Multipart product).
-
Ask Infigo for an editor link (per session)
-
Load that URL inside your iFrame
-
On your page, you create an <iframe> and set its src to the URL from step 4.
-
When a user clicks your “Design” or “Personalise” button, you:
-
Listen for “Add to basket” / “Save” from the editor
-
On the page that hosts the iFrame, your developer includes our small JavaScript communicator.
-
That script listens for events sent from the editor, for example:
-
“Item added to basket”
-
“Project saved”
-
When the user clicks Add to basket inside the embedded editor:
-
the script receives a Job ID / item ID,
-
your system can then decide what to do next (e.g. move to checkout, store as a draft, etc.).
-
Either create an order or just create output
Once the user has finished in the editor, there are two common options:
-
Create a full order in Infigo
Your developer calls our RecordOrder API and passes:
-
the Job ID from the editor
-
customer details, shipping, totals, etc.
This creates a normal Infigo order you can see and manage in the backend.
-
Only request artwork / output
If you don’t want an order in Infigo, your developer can call our output endpoint instead, passing the Job ID so Infigo just generates the PDF / artwork and either:
That’s really it:
Get a token → get an editor link → load it in an iFrame → listen for events → place an order or request output.
When this is useful
This is particularly helpful if you:
-
Run your own customer portal or internal system and want users to stay in your UI while still using Infigo’s Multipart Editor.
-
Have integrations where jobs are set up outside Infigo but you still want to use our editor for artwork and proofing.
-
Want a smoother, more controlled journey for users creating multi-part items (e.g. sets, packs, or grouped pieces) without bouncing them between systems.
Need help?
If you’re already embedding MegaEdit, your technical team can extend that implementation to Multipart using the Academy guide above.
If you’re not yet embedding our editors but would like to, or you’re not sure where to start, just contact our Infigo Support Team and we can:
-
confirm whether embedded editors are a good fit for your use case, and
-
point your team to the right examples and documentation to get set up.