# PipeStock Pro statement of work package

A buyer-signable SOW packet for turning Plumbing Supply Inventory into a paid, rebrandable plumbing supply inventory software for trade counters and regional warehouses pilot with scoped deliverables, acceptance gates, data responsibilities, support terms, change controls, and signature ownership.

Buyer default: Riverbend Plumbing Supply
Recommended tier: Branch inventory pilot
Investment summary: $22k-$40k setup and $1k-$3.5k/month recurring. 45 percent due at signature for branch tenant setup and item master mapping.
Target launch window: Weeks 1-4; 1 week SKU export, 2 weeks scanner and workflow hardening, 2 weeks controlled branch pilot.
SOW term: 5-week branch pilot for one location, one ERP item export, scanner testing, and one product category focus.
Production domain: plumbing-supply.ideas-realized.com
Preview URL: https://plumbing-supply.ideas-realized.com
JSON manifest: /demo-library/plumbing-supply/statement-of-work.json

## Agreement Snapshot

- Product: PipeStock Pro
- Buyer: Riverbend Plumbing Supply
- First proof screen: ops
- First proof URL: https://plumbing-supply.ideas-realized.com?screen=ops

## Scope Modules

- Tenant setup: Branch inventory workspace. Scope: Configure branch, bin zones, supplier labels, product categories, roles, subdomain, and brand tokens. Acceptance: Scanner history and PO receipt panel update; hardware test pending.
- Data onboarding: SKU, bin, receiving, and will-call import. Scope: Map ERP exports, validate barcode aliases, flag missing bins, and stage records for branch review. Acceptance: Count task exposes expected, counted, variance, and adjustment status.
- Workflow configuration: Scanner-assisted operations. Scope: Configure receiving variance review, cycle count status, low-stock alerts, and will-call readiness messages. Acceptance: Pickup board surfaces staged, picking, waiting, and customer-ready states.
- Pilot review: ERP boundary and branch KPI package. Scope: Deliver scanner test results, variance export, will-call readiness report, and ERP posting recommendation. Acceptance: Open the will-call board on mobile with no horizontal overflow and readable pickup states.

## Delivery Milestones

- Kickoff (Week 1, Branch operations lead): Item export, scanner constraints, and branch pilot scope are confirmed. Exit: SKU import and scanner test script approved. Payment: 45 percent due at signature for branch tenant setup and item master mapping.
- Configuration (Weeks 2-3, Implementation lead): Inventory lookup, receiving, counts, will-call, and automation rules are configured. Exit: Branch lead can complete receiving and count scenarios with sample data. Payment: 35 percent due after SKU lookup, receiving session, and cycle count workflow pass branch review.
- Pilot (Weeks 4-5, Counter manager): Team uses the overlay for one category and validates ERP handoff boundaries. Exit: Variance export and will-call readiness report are accepted. Payment: 20 percent due after will-call readiness report and ERP posting recommendation are accepted.

## Acceptance Criteria

- At least 2,500 SKU rows import with required item, bin, and branch fields.
- Scanner acceptance test covers barcode alias, duplicate scan, and manual fallback scenarios.
- Receiving variances and cycle count exceptions can export for ERP review.
- Will-call queue works on mobile without horizontal overflow or unreadable pickup states.
- Item master accepted: Pilot category records loaded with UPC, bin, on-hand, reorder, and supplier fields validated.
- Scanner workflow accepted: Representative barcode scans resolve to the correct SKU, bin, and receiving context.
- ERP boundary approved: Manual export or posting connector path selected with risk notes and next-phase estimate.

## Buyer Responsibilities

- Provide item master and will-call exports before configuration starts.
- Make scanner hardware available for acceptance testing.
- Confirm whether pilot output is read-only, CSV handoff, or approved ERP posting scope.
- ERP item master export with SKU, UPC, bin, branch, stock, reorder, supplier, and unit fields.
- Open purchase order or receiving export for the pilot category.
- Will-call order export or sample pickup queue for one branch.
- Scanner model, barcode examples, and branch operations owner assigned.

## Ideas Realized Responsibilities

- Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.
- A buyer-ready support model for launching Plumbing Supply Inventory with triaged tickets, service levels, training artifacts, success milestones, and renewal proof tied to the first pilot cohort.
- Branch launch thread: Business days during pilot
- Maintain the demo-derived production domain plan for plumbing-supply.ideas-realized.com.

## Data And Security Responsibilities

### Buyer operations owner

- Run a read-only SKU import, validate bin and on-hand values with counter staff, then enable receiving and will-call status updates for the pilot category.
- SKU master: provide 250 to 1,500 SKU records from ERP item export or branch inventory spreadsheet with [object Object], [object Object], [object Object], [object Object].
- Supplier and reorder file: provide 100 to 800 supplier/SKU rows from ERP purchasing export with [object Object], [object Object], [object Object].
- Will-call queue: provide 20 to 90 open will-call orders from Counter order export or inside sales spreadsheet with [object Object], [object Object], [object Object].

### Ideas Realized implementation lead

- The first branch pilot should avoid replacing the ERP. It can use an export/import loop to prove counter lookup, receiving exceptions, and will-call readiness for a controlled product category.
- SKU and bin acceptance: Counter users cannot trust lookup until high-volume SKU and bin records are verified. Resolution: Validate the first 50 SKUs with counter and warehouse staff.
- ERP ownership rule: The pilot must not overwrite ERP quantities without a signed integration rule. Resolution: Run read-only imports and export exceptions until sync ownership is approved.
- Customer pricing exclusion: Price-specific data increases permissions and audit scope. Resolution: Keep customer price fields out of the first branch pilot.

## Support And Service Levels

- Branch launch thread: Business days during pilot; response Next business day. Included: ERP export questions, scanner issues, receiving workflow tuning, and will-call status changes.
- Branch operations review: One 45-minute session per week; response Scheduled. Included: Variance review, scanner results, counter feedback, and ERP boundary decisions.

## Change Orders And Exclusions

- Change control: ERP posting, supplier EDI, or automated purchase order submission: Requires integration review and separate posting/reconciliation scope. Owner: Implementation lead.
- Change control: Additional branches, product categories, or replenishment optimization: Scope after the first branch pilot proves lookup, receiving, and pickup workflows. Owner: Growth lead.
- Exclusion: No ERP writeback or replenishment automation in the base pilot.
- Exclusion: No real-time supplier EDI until source formats and exception rules are approved.
- Exclusion: Cycle count corrections remain review-only until branch leadership approves posting controls.
- Exclusion: Do not promise ERP replacement or real-time inventory authority.
- Exclusion: Do not enable automated stock adjustments without sign-off on posting rules.
- Exclusion: Do not include multi-branch replenishment in the base pilot.

## Legal Review Notes

- This demo SOW package is a sales and implementation planning artifact, not legal advice.
- Final MSA, DPA, payment terms, taxes, procurement language, and security addenda require buyer/legal review before signature.
- No regulated production data should be loaded until data-processing, access, retention, and incident-response terms are approved.

## Signature Blocks

- Client sponsor: Approves budget, pilot scope, and launch decision.
- Buyer operations owner: Provides source data, validates workflow language, and accepts launch criteria.
- Ideas Realized implementation lead: Owns configuration, runbook, QA evidence, and post-pilot backlog recommendation.

## Implementation Handoff Links

- Deal desk package: /demo-library/plumbing-supply/deal-desk
- Deal desk package JSON: /demo-library/plumbing-supply/deal-desk.json
- Procurement pack: /demo-library/plumbing-supply/procurement-pack
- Client proposal: /demo-library/plumbing-supply/client-proposal
- Client launch plan JSON: /demo-library/plumbing-supply/client-launch-plan.json
- Implementation work order: /demo-library/plumbing-supply/implementation-work-order
- Deployment launch plan JSON: /demo-library/plumbing-supply/deployment-launch.json
- Production data contract JSON: /demo-library/plumbing-supply/data-contract.json
- Tenant seed package JSON: /demo-library/plumbing-supply/tenant-seed-package.json
- Buyer launch room: /demo-library/plumbing-supply/launch-room