Estimated Delivery Date, or EDD, is KIBO’s real-time promise engine — it calculates and surfaces a delivery date for shoppers at the Product Detail Page, cart, and checkout, and carries that same date through the fulfillment and admin workflows. The calculation is built from processing time at the fulfillment location, carrier transit time by shipping method, and the shopper’s address — combined differently depending on whether the order is Direct Ship, Delivery, or Pickup.For Direct Ship and Delivery fulfillment types, the transit time component of that calculation is powered by a Shipping Extensibility application — a custom application registered in KIBO’s Developer Center that acts as the bridge between KIBO and whichever carrier or rate service an implementation uses. In this video, we’ll walk through how to build and register that application in the Dev Center, configure a carrier account in the KIBO Admin UI to reference it, and wire up the API extensions that allow the EDD engine to call it at the right moments in the order lifecycle. Estimated Delivery Date, or EDD, is KIBO’s real-time promise engine — it calculates and surfaces a delivery date for shoppers at the Product Detail Page, cart, and checkout, and carries that same date through the fulfillment and admin workflows. The calculation is built from processing time at the fulfillment location, carrier transit time by shipping method, and the shopper’s address — combined differently depending on whether the order is Direct Ship, Delivery, or Pickup. For Direct Ship and Delivery fulfillment types, the transit time component of that calculation is powered by a Shipping Extensibility application — a custom application registered in KIBO’s Developer Center that acts as the bridge between KIBO and whichever carrier or rate service an implementation uses. In this video, we’ll walk through how to build and register that application in the Dev Center, configure a carrier account in the KIBO Admin UI to reference it, and wire up the API extensions that allow the EDD engine to call it at the right moments in the order lifecycle. We’re starting in the KIBO Developer Center, which is a separate administrative portal from the KIBO Admin UI. The Dev Center is where developer accounts, applications, and theme records are created and managed — it’s the environment where code is uploaded, tested, and deployed before reaching production. Every application that extends KIBO’s platform behavior, including the “Shipping Extensibility” application that powers EDD, is here. In this video, we’ll create a new application from scratch and configure it to serve as the EDD shipping adapter. We’re starting in the KIBO Developer Center, which is a separate administrative portal from the KIBO Admin UI. The Dev Center is where developer accounts, applications, and theme records are created and managed — it’s the environment where code is uploaded, tested, and deployed before reaching production. Every application that extends KIBO’s platform behavior, including the “Shipping Extensibility” application that powers EDD, is here. In this video, we’ll create a new application from scratch and configure it to serve as the EDD shipping adapter. To create a new application, we’ll click the “Create Application” button in the upper right corner of the “Applications” page. To create a new application, we’ll click the “Create Application” button in the upper right corner of the “Applications” page. The “Create Application” modal asks for two fields: “Name” and “Application ID”.The “Name” is a human-readable label for the application as it will appear in Dev Center.The “Application ID” is the programmatic identifier that KIBO uses to reference this application in configurations and API calls — we’ll enter both before saving. The “Create Application” modal asks for two fields: “Name” and “Application ID”. The “Name” is a human-readable label for the application as it will appear in Dev Center. The “Application ID” is the programmatic identifier that KIBO uses to reference this application in configurations and API calls — we’ll enter both before saving. With the “Name” and “Application ID” entered, we’ll click “Save” to create the application record. With the “Name” and “Application ID” entered, we’ll click “Save” to create the application record. The new application now appears in the “Applications” list. We’ll click on it to open its configuration page. The new application now appears in the “Applications” list. We’ll click on it to open its configuration page. This is the application’s configuration page. The “Core” tab shows the application’s “Name”, “ID”, “Version”, and “Application Key” — a unique identifier KIBO generates automatically that will be referenced when we connect this application to carrier accounts later.We discussed configuring Applications in a previous video. This is the application’s configuration page. The “Core” tab shows the application’s “Name”, “ID”, “Version”, and “Application Key” — a unique identifier KIBO generates automatically that will be referenced when we connect this application to carrier accounts later. We discussed configuring Applications in a previous video. We’ll click on the “Packages” tab to begin configuring the application’s functional behavior. We’ll click on the “Packages” tab to begin configuring the application’s functional behavior. Inside the Packages section, we’ll click the “Capabilities” tab. Capabilities define what this application is able to do within KIBO’s extensibility framework — this is where we’ll register it as a “Shipping Adapter”, which is the capability type required for EDD transit time calculation. Inside the Packages section, we’ll click the “Capabilities” tab. Capabilities define what this application is able to do within KIBO’s extensibility framework — this is where we’ll register it as a “Shipping Adapter”, which is the capability type required for EDD transit time calculation. On the “Capabilities” tab, we’ll click “Add Capability” to begin adding the “Shipping Adapter” capability to this application. On the “Capabilities” tab, we’ll click “Add Capability” to begin adding the “Shipping Adapter” capability to this application. The “Add Capability” modal presents a dropdown of available capability types. We’ll select “Shipping Adapter”; this is what registers the application as a carrier integration point capable of returning transit time data to the EDD engine. The “Add Capability” modal presents a dropdown of available capability types. We’ll select “Shipping Adapter”; this is what registers the application as a carrier integration point capable of returning transit time data to the EDD engine. With “Shipping Adapter” selected, we’ll click “Ok” to confirm the capability type. With “Shipping Adapter” selected, we’ll click “Ok” to confirm the capability type. The resulting modal is where the Shipping Adapter’s technical configuration is defined.The “Shipping Adapter Endpoint URL” field accepts the URL of the external API or service that KIBO will call to retrieve transit time data. We’ll leave that blank.The “Shipping Adapter Configuration” JSON block defines the service types this adapter supports, including service code suffixes, delivery durations, and locale-specific display names.Important Note: the specific values entered here will depend on the carrier integration and implementation setup. For guidance on how to structure this configuration, reference the KIBO documentation linked to this step. The resulting modal is where the Shipping Adapter’s technical configuration is defined. The “Shipping Adapter Endpoint URL” field accepts the URL of the external API or service that KIBO will call to retrieve transit time data. We’ll leave that blank. The “Shipping Adapter Configuration” JSON block defines the service types this adapter supports, including service code suffixes, delivery durations, and locale-specific display names. Important Note: the specific values entered here will depend on the carrier integration and implementation setup. For guidance on how to structure this configuration, reference the KIBO documentation linked to this step. Once the Shipping Adapter configuration has been populated, we’ll click “Save” to confirm it. Once the Shipping Adapter configuration has been populated, we’ll click “Save” to confirm it. Next, we’ll need to install this Application on our Tenant so we can use it. Back on the “Core” tab, we’ll click the “Install” button on the top right. Next, we’ll need to install this Application on our Tenant so we can use it. Back on the “Core” tab, we’ll click the “Install” button on the top right. This will open a modal window displaying all of the Tenants available in this Dev Account. We’ll scroll through and select the Tenants that need to have access to this Application, then we’ll click “OK”. This will open a modal window displaying all of the Tenants available in this Dev Account. We’ll scroll through and select the Tenants that need to have access to this Application, then we’ll click “OK”. With the “Shipping Adapter” capability created, and the new Application installed on the tenant, we’ll click “Save” at the top of the page to save the full application configuration before moving on. With the “Shipping Adapter” capability created, and the new Application installed on the tenant, we’ll click “Save” at the top of the page to save the full application configuration before moving on. With the “Shipping Extensibility” application configured in the Dev Center and installed on our Tenant, we’ll now move to the KIBO Admin UI to complete the carrier account setup.The first step will be to enable the Application we just built and connected to this Tenant. With the “Shipping Extensibility” application configured in the Dev Center and installed on our Tenant, we’ll now move to the KIBO Admin UI to complete the carrier account setup. The first step will be to enable the Application we just built and connected to this Tenant. In the left menu, on the “SYSTEM” tab, click “Customization”, then click “Applications”. In the left menu, on the “SYSTEM” tab, click “Customization”, then click “Applications”. This is the Applications Menu. All installed Applications on this Tenant are listed here. This is the Applications Menu. All installed Applications on this Tenant are listed here. We’ll click on the Application we just installed to configure it. We’ll click on the Application we just installed to configure it. On the Application details page, we’ll click the slider button next to “Enable Application”. We can now use this Application on this Tenant. On the Application details page, we’ll click the slider button next to “Enable Application”. We can now use this Application on this Tenant. Next, we need to connect the application to KIBO’s shipping configuration so it becomes available as a carrier option for EDD-enabled sites.Back on the “SYSTEM” tab, we’ll click “Settings”, then click “Shipping”. Next, we need to connect the application to KIBO’s shipping configuration so it becomes available as a carrier option for EDD-enabled sites. Back on the “SYSTEM” tab, we’ll click “Settings”, then click “Shipping”. This is the “Shipping” settings page. It contains configuration for “Shipping Methods”, “Carriers”, “Zones”, “Product Rules”, and “Carrier Accounts” across all Sites in the tenant. This is the “Shipping” settings page. It contains configuration for “Shipping Methods”, “Carriers”, “Zones”, “Product Rules”, and “Carrier Accounts” across all Sites in the tenant. We’re here specifically to set up a Carrier Account that references our new “Shipping Extensibility” application, so we’ll navigate to the “Carrier accounts” tab. We’re here specifically to set up a Carrier Account that references our new “Shipping Extensibility” application, so we’ll navigate to the “Carrier accounts” tab. This is the Carrier Accounts page, which shows all accounts previously configured for this tenant. This is the Carrier Accounts page, which shows all accounts previously configured for this tenant. We’ll click “Create New Carrier Account” to create our EDD Carrier Account. We’ll click “Create New Carrier Account” to create our EDD Carrier Account. The “Carrier Types” dropdown lists all carrier integrations available in this tenant — including the native carriers like FedEx and UPS, and our newly registered “Shipping Extensibility” application.This is why we built and configured the application in the Dev Center first — the carrier type only appears in this dropdown once the application has been registered and installed to the tenant. We’ll select “STH EDD Extensibility”. The “Carrier Types” dropdown lists all carrier integrations available in this tenant — including the native carriers like FedEx and UPS, and our newly registered “Shipping Extensibility” application. This is why we built and configured the application in the Dev Center first — the carrier type only appears in this dropdown once the application has been registered and installed to the tenant. We’ll select “STH EDD Extensibility”. With the carrier type selected, we’ll enter a “Nickname” for this account. The nickname is the internal label that will identify this carrier account throughout the shipping configuration. With the carrier type selected, we’ll enter a “Nickname” for this account. The nickname is the internal label that will identify this carrier account throughout the shipping configuration. When we have the new EDD Carrier Account configured, we’ll click “Save” to create it. When we have the new EDD Carrier Account configured, we’ll click “Save” to create it. Now that the Carrier Account exists, we need to associate it with the appropriate Site-level shipping configuration. To do that, we’ll click the “Carriers” tab. Now that the Carrier Account exists, we need to associate it with the appropriate Site-level shipping configuration. To do that, we’ll click the “Carriers” tab. This is the “Carriers” page. Carriers are configured per each Site.We need the “Shipping Methods and Rates” section, where carrier accounts are assigned. We can either scroll down to it or click the link at the top of the page to be navigated to it. This is the “Carriers” page. Carriers are configured per each Site. We need the “Shipping Methods and Rates” section, where carrier accounts are assigned. We can either scroll down to it or click the link at the top of the page to be navigated to it. The “Select Carrier” dropdown lists all available carrier types for this Site. We’ll select “STH EDD Extensibility” to begin configuring it. The “Select Carrier” dropdown lists all available carrier types for this Site. We’ll select “STH EDD Extensibility” to begin configuring it. With the Carrier type selected, a “Carrier Account” dropdown appears. This is where we link the specific Carrier Account we created earlier to this Shipping Method configuration.We’ll select “STH EDD Extensibility Account”, the account we just saved, to connect the two. With the Carrier type selected, a “Carrier Account” dropdown appears. This is where we link the specific Carrier Account we created earlier to this Shipping Method configuration. We’ll select “STH EDD Extensibility Account”, the account we just saved, to connect the two. With the account linked, we’ll check “Enable for Checkout”. This toggle is what makes the EDD Shipping Method visible and available to shoppers during the checkout flow.Important Note: without this checkbox enabled, the Carrier Account exists in the configuration but will not surface at checkout or contribute to EDD calculations for this Site. With the account linked, we’ll check “Enable for Checkout”. This toggle is what makes the EDD Shipping Method visible and available to shoppers during the checkout flow. Important Note: without this checkbox enabled, the Carrier Account exists in the configuration but will not surface at checkout or contribute to EDD calculations for this Site. We’ll click “Save” to commit the Carrier configuration. We’ll click “Save” to commit the Carrier configuration. The final configuration step is registering the “API Extensions” that wire the Shipping Extensibility application into KIBO’s Order and Fulfillment events.Back on the “SYSTEM” tab, we’ll again click on “Customization”, then click “API Extensions”. The final configuration step is registering the “API Extensions” that wire the Shipping Extensibility application into KIBO’s Order and Fulfillment events. Back on the “SYSTEM” tab, we’ll again click on “Customization”, then click “API Extensions”. This is the “API Extensions” editor, where custom functions are registered to KIBO’s platform action points. This allows the EDD engine to calculate and store the delivery date at the moment a shipment is committed.Important Note: the specific JSON required here will depend on the application key and implementation. For the complete configuration reference, consult the KIBO documentation linked to this step.With the extensions saved, the Shipping Extensibility application is fully wired into the platform, and EDD calculation is active for this site. This is the “API Extensions” editor, where custom functions are registered to KIBO’s platform action points. This allows the EDD engine to calculate and store the delivery date at the moment a shipment is committed. Important Note: the specific JSON required here will depend on the application key and implementation. For the complete configuration reference, consult the KIBO documentation linked to this step. With the extensions saved, the Shipping Extensibility application is fully wired into the platform, and EDD calculation is active for this site.