Alloy.ai Statement of Work

Package duration: 2-4 weeks.

The project will be delivered with the following key milestones leading up to delivery of the retailer datasets. The weeks noted below reflect the time it takes to complete each implementation activity once working retailer credentials are provided.

Connect is Alloy.ai’s data partner package. Alloy.ai ingests the End User’s existing retailer data, runs quality checks against the source reports, and delivers the normalized datasets to the data destination the Customer selects. In this Statement of Work, “Customer” means the data partner and “End User” means the brand whose retailer data is in scope. We deliver the dataset, not access to the Alloy.ai platform.

We will provide a detailed project plan with dates and owners after kickoff.

Alloy.ai Project Plan

Phase	Milestone	Week
Kickoff	Kickoff email from Alloy.ai to the End User point of contact, Customer copied; implementation workspace access provisioned for both	1
Credentials	End User enters retailer credentials, or routes credential requests to the retailer owners, in the implementation workspace	1 - 2
Build	Build & Configure: live retailer feeds + historical load (1 or 2 years, as stated in the order agreement)	1 - 3
Quality Checks	Alloy.ai quality checks against the source reports; notice of completion email sent per retailer	2 - 3
Data Destination	Customer configures the data destination; Alloy.ai completes the connection	2 - 4
Data Confirmation	Customer confirms the datasets have arrived and match expectations	3 - 4
Closeout	Closeout email to the Customer, End User copied; transition to support	4

Assumptions

Start Date:	Alloy Technologies Effective Date
Alloy.ai Platform:	Any timeline given for the project during implementation is dependent on the availability of Customer and End User resources for the project. The Alloy.ai stakeholders will raise a project issue/risk if any delay impacts the overall delivery of the project. Any timeline given for the project is dependent on timely access to working retailer credentials.
Support Model:	Connect is run by the Alloy.ai implementation team through the implementation inbox (implementation@alloy.ai). Connect does not include a dedicated Implementation Project Manager or Integration Specialist assignment. During the Term, the Customer provides First Level Support to End Users, and Alloy.ai provides Second Level Support to the Customer, subject to the Alloy.ai Support and Service Level Agreement and Exhibit C. Neither the Customer nor the End User contacts the Alloy.ai Support team directly.
Platform Access:	Users are created for both the Customer and the End User. Both see a scoped “Connect your data sources” view rather than the full Alloy.ai platform. Data-only Alloy.ai access remains for the Customer and the End User after closeout.
Scope of Data:	Alloy.ai is accountable for the following core metrics: sales dollars, sales units, and inventory. Additional fields pass through as the retailer feed provides them. Alloy.ai does not warrant the accuracy or completeness of fields outside the core metrics.
Per-Retailer Timing:	Timings below run from the date Alloy.ai receives working credentials, and apply to retailers Alloy.ai already integrates with. Live feed: connected within two (2) business days. Historical data: loaded within five (5) business days. Portal-ingested history is dependent on the speed of the retailer portal. Data available for share: two (2) to six (6) business days.
Partner Integrations:	Existing Alloy.ai retailer integrations only. Net-new integration work is not included in this package. Customer and End User will be active, accountable parties to help drive urgency in obtaining access to data and resolving data access and data quality issues of source data. If the integration progress is delayed or blocked due to lack of responsiveness or action, then Alloy.ai has the right to pause integration work and re-allocate dedicated resources. Once the integration is unblocked, the integration will be queued for resourcing based on current capacity.
Billing:	Billing begins on the date Alloy.ai ingests the data.
Implementation Services:	The services required to configure, test, and provide overall support for the delivery of the retailer datasets. The activities being provided under Implementation Services are: Implementation coordination through the Alloy.ai implementation inbox Integration Setup / Ingestion of Data Data quality checks Data Destination configuration Notice of completion per retailer Project closeout Each activity below is applicable to each phase of the project.

Not Included

Product master and mapping:	Not implemented for Connect. Transformation of the delivered data into the Customer's schema is owned by the Customer.
Data review (UAT):	Alloy.ai does not perform data review or UAT data delivery for Connect. Alloy.ai runs its own quality checks against the source reports before sending the notice of completion.
Training and enablement:	No live admin or user training. Help articles and in-app documentation are available to both the Customer and the End User.
AI agent configuration:	Not included.
Net-new integrations:	Not included. Connect covers existing Alloy.ai retailer integrations only.
Custom historical:	Not included. Historical is limited to the 1 or 2 years stated in the order agreement, loaded through Alloy.ai's standard process.
Account Manager workstream:	Connect does not include a dedicated Account Manager engagement, executive steering, or change management.
Data lake build:	Standing up or configuring the End User's own data lake or warehouse is owned by the End User.

Phase Activities

Description	Responsible for Completion
Project Kickoff Kickoff email sent from Alloy.ai to the End User point of contact, with the Customer copied Users created for the Customer and the End User; scoped implementation workspace access provisioned Confirm Alloy.ai has the right contacts: the credential owners and the retailer relationship owner Review of the retailer integrations included in scope	Alloy.ai
Customer and End User to provide the following within a week after project kickoff: Admin account email and the exact brand name Retailer credentials, or the owner to route each credential request to Retailer relationship owner Data destination type and the person who owns it	Customer & End User
Connect Retailer Data End User enters the retailer credentials in the implementation workspace. Feeds show a status of “Created” until setup is completed Where the End User does not own a credential, the request can be sent from the workspace to the owner The Customer may assist with retailer setup	Customer & End User
Data Quality Checks Alloy.ai confirms the ingested data matches the raw reports being ingested A notice of completion email is sent to the Customer and the End User for each retailer	Alloy.ai
Data Destination Setup Customer selects the destination: a data warehouse (Snowflake, Redshift, BigQuery, or Databricks) or a file export Customer completes the connection fields and saves; Alloy.ai is notified automatically and completes the connection The share shows as Synced once data is flowing, and Alloy.ai confirms when it is live. Live schema documentation of every table, metric, and attribute is available in-app	Alloy.ai & Customer
Data Confirmation Customer confirms the datasets have arrived in the selected destination and match expectations Alloy.ai will answer questions and can loop in engineering, limited to the core metrics stated in the Assumptions above	Customer
Support During implementation, technical questions and file samples go to implementation@alloy.ai After closeout, the Customer provides First Level Support to End Users, and Alloy.ai provides Second Level Support to the Customer	Alloy.ai & Customer
Project Closeout Closeout email sent to the Customer, with the End User copied, and the project transitions to support Data-only Alloy.ai access remains for both the Customer and the End User The project is complete once all retailers in scope have been delivered and the Customer has confirmed receipt in the data destination	Alloy.ai

Completing and approving these key activities is essential for an on-time implementation. Any approval delays may require a change order to extend the project.

Purpose

The Alloy.ai Essentials Implementation Package is a guided, self-serve implementation that gets a Customer live on Alloy.ai in 1 to 8 weeks. A shared Alloy.ai implementation team supports it asynchronously through the Customer’s implementation inbox.

Essentials Implementation Package at a Glance

Duration	1 to 8 weeks
Delivery model	Shared implementation team, async via implementation inbox; no standing calls
Existing retailer integrations	Up to 10
Net-new integrations	Up to 2 (flat-file feeds only)
Data review turnaround	7 business days (existing integrations)
Training	Self-directed (pre-recorded videos and guides)
AI Agents	Configured during implementation; AM-led enablement after go-live

Service Scope

Alloy.ai and the Customer complete the following tasks together:

Send kickoff instructions and a recorded introduction by email within two weeks of signature.
Provision the account and set up initial Alloy.ai team members, roles, and admin account(s).
Add in-scope integrations through the Implementation Workspace / Quick Setup.
Build and configure up to ten (10) existing retailer integrations.
Build and configure up to two (2) net-new integrations (flat-file feeds only).
Run Alloy.ai data quality checks on every integration.
Complete the first successful import of the Customer’s product master (Alloy-provided format).
Support historical data loads through the Alloy-provided format and help articles.
Set up the Alloy.ai instance, including relevant template dashboards.
Configure the AI Agents included in the Customer’s subscription, tuned to the Customer’s retailers.
Configure the data destination (when purchased).
Provide self-directed training resources for Admins and End Users.
Provide asynchronous go-live support.
Deliver a structured handoff summary and introductions to Support and the Account Manager.

Prerequisites

The Customer provides the following within one week of receiving kickoff instructions:

Data access, retailer portal credentials, and/or sample files for every in-scope integration.
Credentials for all RPA (portal) integrations.
Introductions to the primary points of contact for each data integration.
The product master in the Alloy-provided format.
Customer project members and roles.

The Customer also provisions accounts for any users beyond the initial admin(s).

Limitations

Up to ten (10) existing retailer integrations and up to two (2) net-new integrations. Net-new integrations must be flat-file feeds.
International data is supported through existing feeds only.
Internal data feeds (forecast, inventory, shipments) are not included.
Unit-of-measure and system migrations are not included.
Change management is not included.
No standing project calls. Guidance is provided through In-App Help, product-led implementation tools, help articles, and pre-recorded videos.
No live training. Training is self-directed.
Account Manager-led AI Agent enablement happens after go-live, not during implementation.
Work beyond these limits requires an upgrade to the Advanced or Premier package, or a change order.

Assumptions

The project starts on the Contracted Alloy Technologies Effective Date.
Timelines depend on the Customer making the relevant resources available and on timely access to data. Alloy.ai will raise a project issue or risk if a delay affects delivery.
The Customer is an active, accountable party in getting data access and resolving data access and data quality issues in source data.
If an integration is delayed or blocked by Customer non-responsiveness, including while the Customer is in User Acceptance testing, Alloy.ai may pause that integration and reallocate resources. Once it is unblocked, Alloy.ai queues it based on current capacity.
After implementation, the Customer requests further integration work through their Account Manager, and Alloy.ai queues it under the post-implementation process.
Alloy.ai handles data review requests through the standard review queue. Turnaround is seven (7) business days from when Alloy.ai receives credentials and successfully begins the ingestion of data.
The Customer accepts or rejects the data for each integration within two (2) weeks of data ingestion.
Any delay in completing or approving key activities may result in a change order to extend the project.

Deliverables

Deliverable	Week	Owner
Emailed kickoff instructions	1	Alloy.ai
Account provisioning + integration setup in Quick Setup	1	Alloy.ai
Project checklist with owners	1	Alloy.ai
Retailer integrations built and configured	1 – 6	Alloy.ai & Customer
Product master loaded (Alloy-provided format)	2 – 5	Alloy.ai & Customer
Historical data loaded (Alloy-provided format)	2 – 6	Alloy.ai & Customer
Self-directed training resources	2 – 7	Alloy.ai
UAT / data acceptance (self-guided, standard review queue)	3 – 7	Customer
Go live	4 – 7	Alloy.ai & Customer
Structured handoff summary + Support / AM introductions	7 – 8	Alloy.ai

*Status updates are handled asynchronously through the implementation inbox.

Level of Effort

The package typically takes 1 to 8 weeks from the Alloy.ai contract effective date, pending the customer’s timely response. Overall elapsed time depends on Customer readiness and resource availability.

Business Go-live happens once the product master is loaded, 50% of in-scope integrations are accepted, and Admin access is enabled.

Closeout. The project is complete once the Customer accepts all deliverables. If everything else is complete, Alloy.ai may close the implementation when a remaining integration is:

not accepted within the two (2) week UAT window, with no response from the Customer, or
not ready to begin within two (2) weeks because of Customer dependencies (data access, credentials, sample files, or resourcing).

Document open integrations at closeout with an owner and next step. When the Customer is ready, they notify their Account Manager, and the work is queued based on current capacity.

Terms & Conditions

This document contains the entire scope of the service. Anything not explicitly included above is out of scope. This service is governed by the Customer’s Order Form and the Alloy.ai Standard Terms of Service or an executed Master Agreement.

Last Updated: October 23, 2026

Purpose

The Alloy.ai Advanced Implementation Package gets a Customer live on Alloy.ai in 6 to 12 weeks. A dedicated Implementation Project Manager and Integration Specialist lead it through weekly syncs, with ad hoc data reviews.

Advanced Implementation Package at a Glance

Duration	6 to 12 weeks
Delivery model	Dedicated IPM + Integration Specialist; weekly syncs; ad hoc data reviews
Existing retailer integrations	Unlimited
Net-new integrations	Included
Internal data feeds	Forecast, inventory, shipments
International / global data	Included
UOM / system migration	Included
Data review turnaround	5 business days (existing integrations)
Training	Up to 2 live Admin + up to 3 live End User trainings, plus pre-recorded videos and guides
AI Agents	Configured with the Customer during implementation

Service Scope

Alloy.ai and the Customer complete the following tasks together:

Send a kickoff email, followed by a live Kickoff & Technical Intro call within two weeks of signature. The call covers product master, internal data, and international data discovery.
Confirm the Alloy.ai products and integrations in scope.
Run weekly syncs and status reporting: activities completed, upcoming milestones, open issues, risks, and roadblocks.
Hold Data Deep Dive call(s) as needed, covering internal data (forecast, inventory, shipments) and international data.
Complete the first successful product master import. A dedicated Alloy.ai resource supports product master mapping.
Build and configure all existing retailer integrations and any net-new integrations.
Build and configure internal data feeds (forecast, inventory, shipments), international data, and historical loads.
Support unit-of-measure / system migration.
Run data quality checks on every integration.
Manage historical data loads. If history isn’t available in the portal, Alloy.ai works with the Customer to load the history that is available.
Set up the Alloy.ai instance, including relevant template dashboards.
Configure the data destination (when purchased).
Configure AI Agents with the Customer, tuned to the Customer’s retailers and internal data.
Deliver up to two (2) live Admin and up to three (3) live End User trainings, sized to the Customer, plus pre-recorded videos and guides. Provide recordings of one Admin and one End User training for future use.
Provide go-live support.
Hold a closeout meeting with the IPM and Account Manager, including an executive recap, and transfer knowledge to the Account Manager, Client Solutions, and Support.

Prerequisites

The Customer provides the following within one week of project kickoff:

Data access and/or sample files for every in-scope integration.
Credentials for all RPA (portal) integrations.
Introductions to the primary points of contact for each data integration.
A product master sample.
Customer project members and roles.

The Customer also provisions accounts for any users beyond the initial admin(s).

Limitations

Change management is not included.
Sell-in Shipment data is not included.
Executive Steering is not included.
Live training is capped at two (2) Admin and three (3) End User sessions. Client Solutions provides further training after sign-off.
Work beyond these limits requires an upgrade to the Premier package or a change order.

Assumptions

The project starts on the Contracted Alloy Technologies Effective Date.
Timelines depend on the Customer making the relevant resources available and on timely access to data. Alloy.ai will raise a project issue or risk if a delay affects delivery.
The Customer’s Account Manager is engaged during implementation and takes ownership of the relationship at closeout.
The Customer is an active, accountable party in getting data access and resolving data access and data quality issues in source data.
If an integration is delayed or blocked by Customer non-responsiveness, Alloy.ai may pause that integration and reallocate dedicated resources. Once it is unblocked, Alloy.ai queues it based on current capacity.
Data review turnaround for existing integrations is five (5) business days.
The Customer accepts or rejects the data for each integration within two (2) weeks of data ingestion.
Any delay in completing or approving key activities may result in a change order to extend the project.

Deliverables

Deliverable	Week	Owner
Live Kickoff & Technical Intro call (incl. product master, internal and international data discovery)	1	Alloy.ai
Detailed project plan with dates and owners	Post kickoff	Alloy.ai
Weekly syncs and status reports	Ongoing	Alloy.ai
Retailer integrations built and configured	2 – 10	Alloy.ai & Customer
Internal data feeds + international data + historical load	3 – 10	Alloy.ai & Customer
UAT / data acceptance (collaborative review in weekly syncs)	4 – 11	Alloy.ai & Customer
Live Admin and End User trainings + videos and guides	4 – 10	Alloy.ai
Go live	6 – 10	Alloy.ai & Customer
Closeout meeting with IPM and Account Manager + executive recap	8 – 12	Alloy.ai

Level of Effort

The package typically takes 6 to 12 weeks after the Customer provides data access and retailer points of contact. Elapsed time depends on Customer readiness and resource availability.

Business Go-live occurs once the product master is loaded, core project stakeholders have attended or been offered one admin training session, and the Customer accepts 50% of in-scope integrations.

Closeout. The project is complete once the Customer accepts all deliverables. If everything else is complete, Alloy.ai may close the implementation when a remaining integration is:

not accepted within the two (2) week UAT window, with no response from the Customer, or
not ready to begin within two (2) weeks because of Customer dependencies (data access, credentials, sample files, or resourcing).

Document open integrations at closeout with an owner and next step. Partner onboarding for deprioritized or stalled integrations can continue after implementation, managed by the IPM and/or Client Solutions. When the Customer is ready, they notify their Account Manager, and the work is queued based on current capacity.

Terms & Conditions

Last Updated: October 23, 2026

Purpose

The Alloy.ai Premier Implementation Package is Alloy.ai’s most comprehensive implementation. A dedicated Implementation Project Manager and Senior Integration Consultant lead it through weekly syncs, with ad hoc data and status reviews and Executive Steering throughout.

Premier Implementation Package at a Glance

Duration	Multi-phased rollout, typically 3 to 6 months per phase. Final timeline and phase plan set with the Customer after kickoff.
Delivery model	Dedicated IPM + Senior Integration Consultant; weekly syncs; Executive Steering
Existing retailer integrations	Unlimited
Net-new integrations	Included
Internal data feeds	Forecast, inventory, shipments, including ERP / sell-in
International / global data	Included
UOM / system migration	Included, including UOM conversion in product master
Change management	Included
Data review turnaround	4 business days, first in the review queue
Training	3 live Admin + up to 10 live End User trainings, tailored to retailer and category-owner workstreams
AI Agents	Configured and operationalized to the Customer's use cases.

Service Scope

Alloy.ai and the Customer complete the following tasks together:

Hold a pre-kickoff Sponsor/Priority Alignment call with the Customer’s executive sponsor.
Send a kickoff email, followed within two weeks of signature by a live kickoff call, a live Technical Intro call, and live Discovery sessions.
Build out Alloy.ai team members and roles, and review the in-scope products and integrations.
Create the project timeline from Customer and Alloy.ai inputs.
Run weekly syncs and status reports, ad hoc data and status reviews, and Executive Steering checkpoints with project sponsors.
Hold a Business Objectives and Value call and Data Deep Dive call(s), covering internal data, ERP/sell-in and international data.
Review sample reports for dashboards.
Run technical discovery and design the product master, including unit-of-measure conversion. A dedicated Alloy.ai resource supports mapping, and Alloy.ai completes the first successful import.
Build and configure all existing retailer integrations and any net-new integrations.
Build and configure ERP/sell-in, internal data feeds, international data, and historical loads (managed by Alloy.ai).
Set up Launchpad and template dashboards.
Run data quality checks and configure the data destination (when purchased).
Configure and operationalize AI Agents mapped to the Customer’s use cases.
Develop and deliver three (3) live Admin and up to ten (10) live End User trainings, plus pre-recorded videos and guides. Provide recordings of one Admin and one End User training.
Provide change management support: adoption planning aligned to the Customer’s workstreams and rollout across user groups.
Provide go-live support.
Run a formal closeout: transition plan (as needed) and executive recap (as needed), with knowledge transfer to the Account Manager, Client Solutions, and Support.

Prerequisites

Before kickoff, the Customer provides its project members and roles.

The Customer provides the following within one week of project kickoff:

Current reports in use.
Data access and/or sample files for every in-scope integration.
Credentials for all RPA (portal) integrations.
Introductions to the primary points of contact for each data integration.
A product master sample.
Project timeline inputs.
An executive sponsor available for the Sponsor / Priority Alignment call and Executive Steering checkpoints.

The Customer also provisions accounts for any users beyond the initial admin(s).

Limitations

Training is capped at three (3) Admin and ten (10) End User sessions. Client Solutions provides further training after sign-off.
Third-party or Customer-side system work (for example, changes inside the Customer’s ERP) is not included.
Work outside the products and integrations listed in the Order Form requires a change order.

Assumptions

The project starts on the Contracted Alloy Technologies Effective Date.
Timelines depend on the Customer making the relevant resources available and on timely access to data. Alloy.ai will raise a project issue or risk if a delay affects delivery.
The Customer’s Account Manager is engaged at deal close and stays involved throughout the implementation.
The Customer is an active, accountable party in getting data access and resolving data access and data quality issues in source data.
If an integration is delayed or blocked by Customer non-responsiveness, Alloy.ai may pause that integration and reallocate dedicated resources. Once it is unblocked, Alloy.ai queues it based on current capacity.
Data review is on demand. Turnaround for existing integrations is four (4) business days, and Premier reviews sit first in the review queue.
The Customer accepts or rejects the data for each integration within two (2) weeks of data ingestion.

Deliverables

Weeks are set with the Customer in the project timeline after kickoff.

Deliverable	Phase	Owner
Sponsor / Priority Alignment call, then live Kickoff call	Kickoff	Alloy.ai
Project timeline with dates and owners	Kickoff	Alloy.ai & Customer
Live Technical Intro, Discovery sessions, Business Objectives and Value call, Data Deep Dive(s)	Discovery + Design	Alloy.ai
Product master design, including UOM conversion	Discovery + Design	Alloy.ai
Retailer integrations built and configured	Build	Alloy.ai & Customer
ERP / sell-in + internal data feeds + international data + historical load	Build	Alloy.ai & Customer
Launchpad and template dashboards	Build	Alloy.ai
UAT / data acceptance (on-demand data review)	UAT	Alloy.ai & Customer
Live Admin and End User trainings + change management support	Training & Enablement	Alloy.ai
Go live	Business Go-live	Alloy.ai & Customer
Transition plan, executive recap, playbook handover (incl. AI Agent approval playbook)	Closeout	Alloy.ai
Weekly status reports + Executive Steering checkpoints	Throughout	Alloy.ai

Level of Effort

Duration is set with the Customer after kickoff, based on scope. Elapsed time depends on Customer readiness and resource availability.

Business Go-live happens once the product master is loaded, 50% of in-scope integrations are accepted, and two Admin training sessions and one user group have been trained.

Closeout. The project ends with a formal closeout: transition plan and executive recap. It is complete once the Customer accepts all deliverables. If everything else is complete, Alloy.ai may close the implementation when a remaining integration is:

not accepted within the two (2) week UAT window, with no response from the Customer, or
not ready to begin within two (2) weeks because of Customer dependencies (data access, credentials, sample files, or resourcing).

Terms & Conditions

Last Updated: October 23, 2026

Alloy.ai Statement of Work

Product & Tech

Data Integrations

Data Destinations

Resources

Company