Pro Tip: eKanban Product Orders via API / Integrations when different parts are built

Here's a Quick Tip when using eKanban in the Production Module and your actuals are populated through an API integration. 

Scenario: The line runs a different part number from those scheduled for the line. 

A different part number starts being produced in the pitch details that was not scheduled in eKanban for the line. How does the system respond? 

L2L looks at the part number information sent to it by an integrated software or via API. If the part number information is different than what has been planned in the System, and if there are no near future orders for that Product, the System will change over the line and only list the new part number / Product once as a Changeover. If you have no upcoming cards for that Product, the System only reflects the Actual Parts built. 

The System only posts the data it was sent from the API integration for pitch actuals. If no eKanban Cards are scheduled for a part number/Product, the System just posts the Product Actuals after the Changeover. This is by design and is intended to discourage building parts and Orders that were not planned.