Accelerator · Integration package
Integrated Carrier Core Screens Package
Fuuz accelerator: Integrated carrier screens — shipment, carrier account, and carrier management UIs
Version: 0.0.1 Spec Version: 2.0.0
Overview
This package installs the core user interface screens for the Integrated Carrier shipping system. It provides the carrier-agnostic shipping screens that work with any carrier registered in the system (FedEx, UPS, or future additions) through the Integrated Carrier Router dispatch flow.
Package Contents
integrated-carrier-core-screens/
├── manifest.json
├── package-data.json
├── install/ 3 screens (install steps)
└── preinstall/ 3 preinstall verification steps
Installed Screens (3)
Integrated Carrier Shipment Screen
The primary operator-facing shipping workflow screen. Provides:
- Carrier selection — Dropdown populated from active
IntegratedCarrierrecords - Service level selection — Filtered by selected carrier from
IntegratedCarrierServicerecords - Billing type selection — Filtered by selected carrier from
IntegratedCarrierBillingTyperecords - Shipment details form — Origin/destination address entry, package count, weight, dimensions
- Rate quote — Triggers the
Integrated Carrier Routerwith request type "Rate Quote"; displays returned carrier rates - Label generation — Triggers label generation for the selected service and rate; invokes
Integrated Carrier Print Labels Standardupon success - Void label — Cancels a previously generated label via the router
- Shipment history — Recent
IntegratedCarrierRequestrecords for the current session
Carrier Account Configuration Screen
Administrative screen for managing carrier accounts:
- Create and edit
IntegratedCarrierAccountrecords (account number, API credentials, test/production environment toggle) - Link accounts to
IntegratedCarrierConnectionConfigurationrecords - Test connectivity to carrier API endpoints
- View connection status and last successful API call
Carrier Management Screen
Administrative screen for managing the carrier registry:
- List of registered
IntegratedCarrierrecords with active/inactive status IntegratedCarrierServicemanagement — add/edit available service levels per carrierIntegratedCarrierBillingTypemanagement — configure billing options per carrierIntegratedCarrierRequestFlowmapping — assign request handler flow IDs to each carrier/request-type combination
Install Process
Preinstall (3 steps): Verifies that none of the 3 screen IDs already exist, preventing duplicate installations.
Install (3 steps): Creates each screen header and its latest version, then deploys to make it available in the Fuuz application.
Installation
- Install
package-integrated-carrier-core-schema-acceleratorandpackage-integrated-carrier-core-flows-acceleratorfirst - Import this package via Fuuz Package Manager
- Install carrier-specific packages (FedEx, UPS) to populate carrier/service/billing seed data
- Assign the Integrated Carrier Shipment Screen to relevant user roles via the Fuuz Role manager
- Add the screen to the navigation menu for shipping users
Dependencies
package-integrated-carrier-core-schema-accelerator— requiredpackage-integrated-carrier-core-flows-accelerator— required (screens invoke the router flows)- At least one carrier package (FedEx or UPS) for seed data to populate carrier dropdowns
Part of the Integrated Carrier Suite
| Package | Description |
|---|---|
integrated-carrier-core-schema |
Data models |
integrated-carrier-core-flows |
Router and print flows |
| integrated-carrier-core-screens (this) | Shipment management screens |
integrated-carrier-fedex |
FedEx seed data and label flows |
integrated-carrier-ups |
UPS seed data and label flows |
integrated-carrier-addon-plex |
Plex ERP integration extension |
Built on the Fuuz Industrial Operations Platform
Before you install
A Jump Start, Not A Finished Answer
An accelerator is a pre-built, configurable starting point that addresses the bulk of the common challenges in its domain. It is not intended to solve every possible variation off the shelf — requirements that fall outside it are expected and normal for the model, not a shortcoming of this one.
Standard
Delivered and working as-is. No configuration needed.
Configurable
A base capability you adapt with the platform's own no-code and low-code tools — screen builder, transforms, workflow rules, flow parameters — without professional services.
Custom development
Feasible on the platform but outside this accelerator's current scope. A scoped change through Fuuz or a certified partner.
Once installed, it is yours
Installation forks the flows, models and screens into your environment as your own copies. Later versions published against this accelerator do not propagate to you automatically — picking up a change means deliberately re-applying it.