Outputs Vs Orders for Iframe Workflows | COREIF_006

0:00 In this tutorial we're covering a key iframe fundamental, and this is the difference between generating an output versus creating an order in Infigo, and why your team will be talking about job IDs.
0:13 So this applies whether you're a standard iframe customer managing your own platform and storefront, or a Print IQ iFrame customer, where the storefront is largely handed over.
0:23 The storefront experience may differ, but the embedded experience is the editor workflow still relies on the same core pieces. That's products, customers, and a job ID, which is captured from the editor journey.
0:36 so here's the simplest way to think about it. Your integration requests a link to load the editor in an iframe for a specific customer and a specific product.
0:46 That link automatically authenticates the user and is only valid for a short period. the product ID. When the user completes personalization in the embedded editor, your integration listens for events using the communicator library.
1:06 One of the most important moments is the add to basket or add to cart click event. When that event occurs, you must capture the job ID included in the event data because it's required later to make sure correct output is generated and or the correct job is attached to the order.
1:24 Now once you have the job ID there are two common paths that you'll see described in the iframe documentation you'll see once you've completed this series.
1:32 Path A is output only. In this approach you avoid creating an order in Infigo and instead create output or artwork directly via the API.
1:42 This is useful when your own platform handles checkout and order management. and you simply need a PDF or print-ready artwork generated from the job without placing an order in Infigo.
1:55 Path B is the is to actually create the order within your Infigo system itself. In this approach your e-commerce platform still owns the customer facing basket, cart and checkout but when the customer places an order your system calls the record order endpoint in Infigo.
2:13 That creates the order inside Infigo linked to the job ID you captured from the editor journey. Now related to this there are a couple of high level constraints that are worth being aware of.
2:27 First, order compatibility depends on customer linkage. In Infigo, only registered customers, not guests, can place orders. And an order can only contain jobs associated with a single customer ID.
2:42 So your integration needs to keep customer references consistent across the session. Second, there are common order creation constraints. Your external product must match the Infigo product.
2:55 And shipping addresses must use countries and states that exist in Infigo. otherwise record order can fail. So finally, where does the Infigo admin come into all of this?
3:06 If your workflow creates orders inside Infigo itself, you'll manage and review them in the normal admin areas inside the system.
3:14 One of these is sales orders. This is more associated with your sales personnel and they can see and amend individual orders.
3:26 And then we also have the shared print operations area. And this is for the job level, and this is for the job level operational view.
3:32 We'll cover those screens and the day-to-day workflow in the next tutorial.