
GITNUXSOFTWARE ADVICE
Automotive ServicesTop 10 Best Ecu Program Software of 2026
Top 10 Ecu Program Software tools ranked for ECU coding, including Shop-Ware, Hibou, and AutoLeap, with feature tradeoffs for buyers.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Shop-Ware
Commerce event system powering granular promotions, automations, and integration triggers
Built for e-commerce and B2B teams needing extensible, multi-channel storefront operations.
Hibou
Editor pickDocument generation from rule-driven ECU workflow templates
Built for eCU program teams needing automated documents and audit-ready workflows.
AutoLeap
Editor pickVehicle and ECU driven workflow builder for remap program assembly and deployment
Built for shops needing repeatable ECU programming workflows across common vehicle lines.
Related reading
Comparison Table
This comparison table ranks Shop-Ware, Hibou, AutoLeap, Route4Me, Deputy, and other Ecu Program Software tools by integration depth, focusing on how each system maps its data model and schema into connected workflows. It also compares automation and API surface for provisioning, configuration, extensibility, and throughput, alongside admin and governance controls such as RBAC, audit log coverage, and policy enforcement. The table highlights tradeoffs that affect implementation and ongoing operations across multi-team environments.
Shop-Ware
shop managementProvides automotive shop management for estimating, repair orders, parts, invoicing, and customer communication.
Commerce event system powering granular promotions, automations, and integration triggers
Shop-Ware stands out with its modular commerce architecture built on a service-based backend and themable storefront. It supports core e-commerce capabilities like catalog management, product variations, pricing rules, promotions, and order management across multiple sales channels.
Deep extensibility via a plugin ecosystem enables ERP, payment, and shipping integrations without replacing the whole system. Built-in B2B features such as customer segmentation, role-based permissions, and quote-style workflows make it usable beyond standard online retail.
- +Modular architecture supports extensive customization through plugins
- +Strong storefront theming with reusable components for faster UI changes
- +Robust catalog, pricing, and promotion rules cover complex storefront needs
- +B2B features include roles, customer segmentation, and account controls
- –Admin workflows require configuration discipline to avoid rule conflicts
- –Advanced setup and integration tasks can demand developer support
- –Performance tuning is often needed for heavy catalogs and custom extensions
- –Plugin compatibility across versions can add operational maintenance overhead
E-commerce operations managers
Run multi-channel catalogs and promotions
Fewer merchandising errors
Enterprise B2B sales teams
Manage roles, accounts, and quotes
Faster quote-to-order cycles
Show 1 more scenario
IT integration and platform teams
Connect ERP, payments, and shipping
Lower integration effort
A plugin-driven architecture allows targeted integrations without replacing the commerce core.
Best for: E-commerce and B2B teams needing extensible, multi-channel storefront operations
More related reading
Hibou
dealer workflowCombines automotive repair shop software with marketing tools, online booking workflows, and estimate-to-invoice processes.
Document generation from rule-driven ECU workflow templates
Hibou stands out with document automation built around ECU program workflows and structured outputs. Core capabilities include intake, rule-based routing, and generation of standardized artifacts for program teams.
The system supports audit-friendly trails so stakeholders can track changes across process steps. Workflow configuration focuses on repeatable operations instead of ad-hoc file handling.
- +Rule-based workflow design supports repeatable ECU program operations
- +Document generation templates reduce manual creation of standardized outputs
- +Activity trails help audit handoffs across workflow steps
- +Structured intake fields improve data consistency for program reporting
- –Complex rule sets can feel heavy for smaller ECU teams
- –Template customization requires more setup than simple form filling
- –Reporting depth may lag dedicated analytics tools for ECU programs
- –Advanced workflow tuning can slow down iteration cycles
ECU program operations teams
Automate document generation per program steps
Faster program document turnaround
Compliance and audit coordinators
Track changes across enrichment stages
Reduced audit preparation effort
Show 2 more scenarios
Legal review and case teams
Route structured drafts for review
Fewer review back-and-forth cycles
Rule-based routing sends documents to the right reviewers based on predefined ECU program criteria.
Program data management leads
Maintain consistent output schemas
More reliable downstream reporting
Structured outputs standardize fields across program teams and reduce manual reconciliation work.
Best for: ECU program teams needing automated documents and audit-ready workflows
AutoLeap
workflow automationOffers automotive shop management features including workflow automation, digital inspections, and customer estimate handling.
Vehicle and ECU driven workflow builder for remap program assembly and deployment
AutoLeap is positioned as ECU Program Software focused on turning vehicle and ECU selection inputs into an assembly plan for programming datasets. The workflow-oriented approach emphasizes repeatable file handling, programming sequence configuration, and verification steps instead of manual remap scripts. The fit signal is the emphasis on guided program generation that stays consistent across repeated remapping jobs.
A practical tradeoff is that guided program assembly can constrain custom, one-off sequences when the required ECU process deviates from supported patterns. The tool fits best for shops running frequent ECU programming requests that share similar workflows and need consistent dataset packaging, programming order, and verification checkpoints.
- +Guided ECU workflow reduces remap file preparation errors
- +Vehicle and ECU selection streamlines repeat jobs
- +Programming sequence setup supports consistent technician outcomes
- +Verification steps improve confidence before final write
- –Workflow depth can feel heavy for one-off programming
- –Coverage depends on supported ECU and model combinations
- –Advanced tuning options require additional operational discipline
- –Verification capabilities may not replace bench-level diagnostics
ECU remap technicians
Standardize multi-ECU programming steps
Fewer workflow mistakes
Vehicle calibration shops
Batch remapping with consistent sequencing
Higher throughput
Show 2 more scenarios
Technical support teams
Reproduce failed programming attempts
Faster issue resolution
Verification-oriented steps help capture the same configuration used during a prior ECU programming run.
Operations managers
Control quality across remap workflows
More consistent outcomes
Repeatable program assembly reduces variation between technicians during dataset generation and deployment.
Best for: Shops needing repeatable ECU programming workflows across common vehicle lines
Route4Me
dispatch and routingSupports automotive service route planning with scheduling, driver assignment, and optimized stop sequencing.
Multi-constraint route optimization that sequences stops using time windows and capacity limits
Route4Me stands out with highly structured route optimization workflows built for multi-stop delivery planning. Core capabilities include address import, automated route building, and optimization based on capacity, time windows, and service constraints.
The system also supports ongoing route management with mobile-friendly execution for drivers and team dispatch visibility. Strong suitability emerges for Ecu Program Software use cases focused on field logistics, stop sequencing, and operational coordination.
- +Automates multi-stop route optimization with time window and constraint support
- +Dispatch and driver execution tools keep assignments updated during operations
- +Visual route planning helps validate stop sequences before deployment
- –Setup of constraints and imports can require process tuning
- –Advanced optimization can feel complex compared with simpler ECUs
- –Large network changes may require re-optimizing to stay accurate
Best for: Mid-size logistics teams optimizing multi-stop delivery routes and execution
Deputy
workforce schedulingManages workforce scheduling and shift coverage used by automotive service teams handling Ecu Program service capacity.
Mobile checklists with job instructions and proof-of-completion per shift
Deputy stands out with a front-line workforce scheduling and task-execution workflow built for shift-based operations. It supports employee time and attendance, shift scheduling, and standardized job instructions through mobile checklists.
Managers can monitor compliance and performance signals in real time, using configurable workflows rather than custom code. The system also integrates with HR and payroll tools to keep employee and labor data consistent across the operation.
- +Mobile checklists drive consistent task execution across locations
- +Scheduling and time capture reduce manual updates between managers and staff
- +Configurable workflows support role-based tasks and approvals
- –Advanced workflow tailoring can require operational process redesign
- –Some reporting needs structured setup to reflect real labor KPIs
- –Multi-location governance can add friction for large orgs
Best for: Operations teams standardizing shift workflows with mobile execution and scheduling
monday.com
work managementProvides work management boards and automations for tracking ECU Program inventory, service status, and approvals.
Workflow automations with triggers, conditions, and actions across linked boards
monday.com stands out with highly configurable workboards that model ECU program work as tasks, milestones, and dependency views. Teams can plan ECU deliverables using workflow automations, custom fields, dashboards, and approvals tied to board activity.
Integration options support syncing ECU program data across common productivity and development tools while keeping status visibility in one place. Reporting can combine board metrics into charts and filters for executive and program-level oversight.
- +Highly configurable boards with custom fields for ECU program tracking
- +Workflow automations reduce manual status updates and handoffs
- +Dashboards and reporting summarize progress across multiple workstreams
- +Flexible views like timelines and Kanban support ECU milestones
- –Complex workflow setups can feel heavy for large ECU programs
- –Dashboard definitions require consistent field usage to stay reliable
- –Automation logic can become difficult to troubleshoot over time
- –Advanced governance needs careful permissions and board design
Best for: Mid-size ECU program teams managing milestones, workflows, and reporting
Asana
project workflowSupports task tracking and workflow views for coordinating ECU Program service requests and internal handoffs.
Workload view
Asana stands out with work management that maps tasks to shared goals using timelines, boards, and dashboards in one workspace. Core capabilities include project templates, task dependencies, recurring work, and workload views that help plan and balance execution.
Collaboration features like comments, @mentions, attachments, approvals, and rules for automation support consistent delivery across teams. Reporting and integrations connect Asana work to broader systems through reporting apps, APIs, and native connectors.
- +Task dependencies and rules reduce project slippage
- +Workload view helps managers balance capacity across projects
- +Advanced dashboards summarize progress with filters and recurring reports
- +Robust permissions keep external and internal collaboration organized
- –Complex workflows can require careful setup to avoid clutter
- –Reporting depth depends heavily on how projects are structured
- –Large portfolios can become slow if many teams build custom views
Best for: Program teams needing structured task workflows, visibility, and approvals
ADP Workforce Now
HR and schedulingProvides workforce management and HR services that support automotive service programs with scheduling, time tracking, and compliance reporting.
Time and attendance with configurable payroll-relevant rules and approval workflows
ADP Workforce Now stands out with deep HR, payroll, and time management built into one integrated suite. The platform supports employee data, time and attendance processing, payroll calculation workflows, and configurable HR processes for many global and multi-site organizations.
Standard reporting and analytics cover workforce trends, labor metrics, and compliance-oriented outputs that many Ecu Program Software efforts rely on for operational visibility. Implementation and ongoing administration can be demanding because the solution depends on detailed configuration of roles, calendars, policies, and data feeds.
- +Unified HR, time, and payroll workflows reduce handoff complexity
- +Configurable approvals and policy controls support repeatable Ecu program processes
- +Strong workforce reporting for labor metrics and operational visibility
- –Configuration workload is high for calendars, rules, and approval structures
- –User experience can feel complex for casual managers and occasional admins
- –Integration projects can require specialist effort for clean data synchronization
Best for: Mid-size to enterprise teams running standardized HR and labor operations at scale
UKG Pro
workforce managementDelivers HR and workforce management workflows for automotive service organizations with recruiting, time tracking, and shift scheduling.
Workforce Management scheduling tied to time, absence, and downstream HR and payroll processing
UKG Pro stands out for tightly integrating human resources, workforce management, and payroll into one system built for enterprise operations. It supports core Ecu Program Software needs like role-based workflows, configurable approvals, employee data governance, and workforce planning activities.
Strong time and labor capabilities connect schedules, time capture, and absence reporting to HR and payroll outcomes. The solution also offers extensive reporting and integrations through its platform approach for organizations with complex HR and workforce processes.
- +Integrated HR, time, absence, and payroll data reduces cross-system reconciliation work
- +Configurable workflows and approvals support structured Ecu Program Software processes
- +Robust reporting and analytics help track compliance and program outcomes
- –Setup and configuration complexity can require specialized implementation support
- –User experience can feel heavy for high-frequency operational tasks
- –Advanced analytics often depend on configuration and data quality maintenance
Best for: Enterprises needing integrated HR and workforce execution workflows at scale
SAP S/4HANA Cloud
enterprise ERPOffers ERP capabilities for automotive service operations with finance, procurement, inventory, and service management processes.
Embedded business processes with workflow-driven approvals across S/4HANA Cloud modules
SAP S/4HANA Cloud is distinct for running core ERP processes on an in-memory HANA foundation with cloud delivery and controlled extensibility. It supports finance, procurement, inventory, manufacturing, sales, and customer service with integrated analytics and shared master data across modules.
For Ecu Program Software needs, it offers structured product, demand, and logistics execution paths that connect engineering data to downstream planning and financial outcomes. Built-in automation such as workflow approvals and embedded compliance features reduce manual handoffs across cross-functional teams.
- +In-memory ERP core with tight integration across finance, procurement, and operations
- +Embedded analytics ties operational events to financial reporting in one dataset
- +Workflow and approval controls support consistent execution across business roles
- +Extensibility options integrate custom logic without breaking standard processes
- –Cloud ERP process design can require significant change management and adoption
- –Reporting and data modeling flexibility can be constrained versus fully custom stacks
- –Complex global rollouts increase integration and configuration effort
- –Customization for niche workflows may require development skills and governance
Best for: Enterprises standardizing ERP execution for product, logistics, and financial traceability
Conclusion
After evaluating 10 automotive services, Shop-Ware stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right Ecu Program Software
This buyer's guide covers how to choose Ecu program software across Shop-Ware, Hibou, AutoLeap, Route4Me, Deputy, monday.com, Asana, ADP Workforce Now, UKG Pro, and SAP S/4HANA Cloud.
The focus stays on integration depth, the data model used to represent ECU program work, and the automation plus API surface available for provisioning and governance.
It also highlights admin controls like RBAC-style permissions, approval flows, audit trails, and how each tool handles change tracking across steps.
ECU program execution systems that turn inputs into controlled workflows and auditable outputs
Ecu Program Software is used to manage structured ECU program work that starts with intake and routing, then produces standardized artifacts or datasets, and finally drives downstream execution steps with approvals and verification.
In practice, Hibou focuses on document generation from rule-driven ECU workflow templates, while AutoLeap emphasizes a vehicle and ECU driven workflow builder for remap program assembly and deployment.
Teams use these systems to reduce manual file handling, keep program steps consistent across repeat jobs, and maintain traceability across handoffs from intake to final verification.
Evaluation criteria for ECU program platforms: data model, automation surface, and governance
Tool fit depends on how the system represents ECU program work as structured records and how those records move through repeatable steps.
Integration depth and automation or API support matter most when ECU program operations need to connect to ERP, HR, delivery logistics, or custom tooling without rewriting every workflow.
Governance also matters because approval gates, role-based access controls, and audit logs must reliably protect ECU program decisions and artifacts.
Rule-driven ECU workflow templates with audit trails
Hibou models ECU program steps as rule-based workflows and generates standardized documents from templates, with audit-friendly trails that track changes across steps. This pairing matters when ECU program teams need repeatable routing and evidence of what changed between intake and final outputs.
Vehicle and ECU guided program assembly with verification checkpoints
AutoLeap builds remap program assembly using vehicle and ECU selection inputs and includes programming sequence setup with verification steps. This reduces remap file preparation errors for shops running frequent ECU programming requests that share similar workflows and need consistent dataset packaging.
Commerce event triggers and automation hooks for program-adjacent operations
Shop-Ware includes a commerce event system that powers granular promotions, automations, and integration triggers. This matters when ECU program operations need to coordinate customer-facing storefront events, B2B account workflows, and downstream fulfillment steps using consistent event-driven integration.
Multi-constraint optimization workflows for field logistics execution
Route4Me provides multi-constraint route optimization that sequences stops using time windows and capacity limits and supports dispatch and driver execution. This helps teams that treat ECU program execution as a field logistics problem where stop sequencing accuracy affects throughput.
Board-based ECU program tracking with automation triggers and conditions
monday.com models ECU program work as tasks and milestones in configurable workboards and supports workflow automations with triggers, conditions, and actions across linked boards. This matters when ECU program teams need a visible state machine for deliverables and want automation tied directly to board events.
Task dependency management and recurring work for ECU handoffs
Asana supports task dependencies, recurring work, approvals, and rule-based automation tied to work items. This fits ECU program operations that need structured internal handoffs and workload planning using timelines and dashboards.
Workforce scheduling and time capture rules tied to approvals
Deputy provides mobile checklists with proof-of-completion per shift and configurable workflows for role-based tasks and approvals, while ADP Workforce Now and UKG Pro connect scheduling to time, absence, and downstream payroll-related workflows. This matters when ECU program capacity planning depends on labor compliance, approvals, and consistent time and attendance records across locations.
Choose the ECU program tool that matches the workflow state you must govern
The decision starts with the workflow state that must be governed as structured data, not just tracked as notes.
Then the decision turns to how automation is deployed, whether actions are configured in an admin UI, driven by an API, or assembled through templates that produce artifacts.
Map the ECU program outputs that must be generated or assembled
If ECU program work ends with standardized documents, Hibou fits because it generates artifacts from rule-driven ECU workflow templates with structured intake fields. If ECU program work ends with remap program assembly and dataset packaging, AutoLeap fits because it uses vehicle and ECU selection to build a guided programming sequence with verification steps.
Confirm the tool’s data model supports your workflow steps as records
monday.com supports ECU program tracking by modeling work as tasks, milestones, dependencies, and custom fields inside boards. Asana supports the same concept with tasks, dependencies, approvals, and recurring work, which is useful when ECU program steps must be standardized across repeatable internal handoffs.
Evaluate the automation and integration surface used to move work across systems
Shop-Ware uses a commerce event system that powers granular promotions, automations, and integration triggers, which supports event-driven coordination for B2B workflows. Deputy, ADP Workforce Now, and UKG Pro each connect execution with labor data through configurable approvals and scheduling tied to time and attendance workflows, which reduces manual reconciliation between HR systems and operational checklists.
Test governance controls against real ECU program handoffs
For auditability across workflow steps, Hibou’s audit-friendly trails and template-driven document generation reduce ambiguity between stages. For operational approvals and consistency across shifts, Deputy’s mobile checklists with proof-of-completion and configurable workflows support governance at the moment work is performed.
Check whether logistics sequencing is part of the ECU program workflow
If ECU program throughput depends on field stop sequencing, Route4Me fits because it sequences stops using time windows and capacity limits and keeps assignments updated during dispatch. If ECU program work is primarily internal planning and approvals, monday.com or Asana usually maps better to milestone tracking and dependency-driven handoffs.
Verify whether enterprise ERP control is required for financial and inventory traceability
SAP S/4HANA Cloud is the fit when ECU program execution requires finance, procurement, inventory, and service process controls tied to embedded workflow approvals and shared master data. This choice typically replaces multiple disconnected systems because it connects operational events to embedded analytics and workflow-driven approvals across modules.
Which organizations benefit from ECU program workflow and execution control
Different ECU program environments optimize for different control points, like document output, remap dataset packaging, internal handoffs, or labor compliance.
The right tool depends on which workflow step must be governed as structured data and which integration needs must be handled through automation or API-driven surface.
ECU program teams that must generate audit-ready program documents
Hibou is built for document generation from rule-driven ECU workflow templates with audit-friendly trails and configurable routing tied to roles and process stages.
Shops that run frequent ECU remapping jobs with repeated vehicle and ECU patterns
AutoLeap fits because it uses vehicle and ECU selection to assemble remap program datasets through a guided workflow and verification steps that reduce preparation errors.
Mid-size ECU program teams managing milestones, dependencies, and approvals
monday.com fits when ECU work needs configurable boards with custom fields and workflow automations using triggers, conditions, and actions. Asana fits when ECU work needs dependency management, recurring work, and approvals with workload view for capacity balancing.
Operations teams whose ECU program throughput depends on shift execution and proof-of-completion
Deputy fits because mobile checklists drive consistent task execution with proof-of-completion per shift and configurable role-based workflows and approvals.
Enterprises requiring workforce systems or ERP governance across ECU program execution
ADP Workforce Now and UKG Pro fit when scheduling ties into time capture, absence reporting, and downstream payroll-relevant approvals at scale. SAP S/4HANA Cloud fits when ECU program execution must connect to finance, procurement, inventory, and workflow approvals in one governed ERP data model.
Common failure points when implementing ECU program workflow tools
Most implementation failures come from mismatches between the ECU workflow that must be standardized and the way the tool models that workflow as structured data and automation.
Operational drift also happens when rule sets, templates, or automation logic are configured without enough discipline for the change volume in ECU programs.
Building complex rule sets without governance for conflicts
Hibou’s rule-based workflow design can feel heavy when ECU teams build complex rule sets without a disciplined routing model. To avoid conflicts, keep routing aligned to roles and process stages and validate template outputs after each workflow change.
Overfitting the ECU assembly workflow to one-off programming sequences
AutoLeap’s guided program assembly can constrain custom, one-off sequences when required ECU processing deviates from supported patterns. The corrective action is to treat guided flows as a baseline and isolate exceptions into separate workflows that still preserve packaging and verification checkpoints.
Allowing automation logic to drift as boards and fields change
monday.com workflow automations can become difficult to troubleshoot over time when linked boards and custom fields are modified inconsistently. The mitigation is to standardize field names and milestones, then validate that automation triggers still fire correctly when dependencies or board structures evolve.
Using workforce scheduling tools for ECU program work that needs artifact templating
Deputy and HR-first systems focus on shift execution, time capture, and compliance approvals, which does not replace ECU document generation or remap dataset assembly. If artifacts and audit-ready outputs are the core deliverables, Hibou or AutoLeap are better aligned than Deputy or HR suites alone.
Treating logistics stop sequencing as an ad hoc planning task
Route4Me’s strength depends on setting constraints like time windows and capacity limits, and it can require process tuning when imports and constraints are not modeled correctly. When ECU program execution depends on dispatch timing, Route4Me should be configured with constraints that match real operating limits rather than using simplified assumptions.
How We Selected and Ranked These Tools
We evaluated Shop-Ware, Hibou, AutoLeap, Route4Me, Deputy, monday.com, Asana, ADP Workforce Now, UKG Pro, and SAP S/4HANA Cloud by scoring each tool on features, ease of use, and value, then combining those scores into an overall rating with features carrying the most weight at 40 percent.
The features score prioritized integration depth, the practical data model used to represent ECU program work, and the automation and governance controls that support provisioning, approvals, and traceability across steps.
Ease of use measured how directly teams can model workflows and maintain them without turning configuration into ongoing engineering work.
Shop-Ware separated from lower-ranked tools because its commerce event system powers granular promotions, automations, and integration triggers, which lifted it on integration depth and automation surface and supported stronger overall features scoring.
Frequently Asked Questions About Ecu Program Software
How should teams choose between Shop-Ware, Hibou, and AutoLeap for ECU program workflows?
What integration and API patterns matter most for Ecu Program Software?
Which tool best supports SSO and RBAC for operational control?
How do teams migrate existing ECU program data models into a new system?
What admin controls help reduce configuration drift during ECU program execution?
How does each tool handle auditability and change tracking for ECU process steps?
Which tool is best suited for repeatable programming dataset assembly from vehicle and ECU inputs?
How should a team model ECU program dependencies and approvals across workstreams?
What are common failure modes when configuring ECU program workflows, and how can tools mitigate them?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Automotive Services alternatives
See side-by-side comparisons of automotive services tools and pick the right one for your stack.
Compare automotive services tools→FOR SOFTWARE VENDORS
Not on this list? Let’s fix that.
Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.
Apply for a ListingWHAT THIS INCLUDES
Where buyers compare
Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.
Editorial write-up
We describe your product in our own words and check the facts before anything goes live.
On-page brand presence
You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.
Kept up to date
We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.
