# PipeStock Pro pilot proposal A client-ready proposal for turning the Plumbing Supply Inventory demo into a scoped, rebrandable trade supply inventory software pilot with clear launch owners, commercial terms, acceptance criteria, and follow-on SEO/AEO expansion. Recommended offer: Trade supply inventory software pilot package Investment summary: $22k-$40k setup, $1k-$3.5k/month recurring, $1k-$3.5k/month hosting, import support, scanner testing, and workflow iteration. Target launch window: Weeks 1-4; 1 week SKU export, 2 weeks scanner and workflow hardening, 2 weeks controlled branch pilot. ## Executive Narrative A rebrandable trade counter inventory control layer for supply houses that need faster SKU lookup, receiving, cycle counts, and will-call visibility. The paid pilot keeps scope tight: prove faster counter service, fewer blind bin checks, and cleaner reorder decisions for branch managers. while deferring custom integrations, advanced automation, and unsupported workflow expansion until the buyer validates adoption. Buyer outcome: Faster counter service, fewer blind bin checks, and cleaner reorder decisions for branch managers. Proof points: - Lookup acceptance: Branch users validate 50 high-volume SKUs with bin and substitute context.. Evidence: SKU lookup and scanner event acceptance test. - Receiving exception capture: 100% of pilot PO variances captured with quantity, SKU, and disposition.. Evidence: Receiving session table. - Will-call status completeness: 90% of pilot will-call orders have ready, hold, or missing-part status.. Evidence: Will-call queue. - Counter service speed: Reduce repeated SKU/bin searches across the pilot category. modeled lift. - Receiving accuracy: Capture receiving exceptions at the scanner event level. modeled lift. ## Prospect Fit - Runs a trade counter, warehouse, or regional branch with thousands of SKUs. - Counter staff frequently call the warehouse to confirm stock, bins, or will-call status. - ERP screens are too slow or too broad for front-line counter workflows. - Branch managers and Counter sales managers can validate the pilot without replacing their core system. ## Scope ### Tenant setup Configure branch, bin zones, supplier labels, product categories, roles, subdomain, and brand tokens. Deliverables: - Branch inventory workspace - SKU search with bin location, stock, supplier, and reorder pressure - SKU import template - SKU master import map Acceptance: Scanner history and PO receipt panel update; hardware test pending. ### Data onboarding Map ERP exports, validate barcode aliases, flag missing bins, and stage records for branch review. Deliverables: - SKU, bin, receiving, and will-call import - Receiving session with barcode entry and variance review - Scanner test script - Supplier and reorder file import map Acceptance: Count task exposes expected, counted, variance, and adjustment status. ### Workflow configuration Configure receiving variance review, cycle count status, low-stock alerts, and will-call readiness messages. Deliverables: - Scanner-assisted operations - Cycle count workflow with expected-versus-counted status - Receiving variance export - Will-call queue import map Acceptance: Pickup board surfaces staged, picking, waiting, and customer-ready states. ### Pilot review Deliver scanner test results, variance export, will-call readiness report, and ERP posting recommendation. Deliverables: - ERP boundary and branch KPI package - Will-call queue with readiness, exception, and counter handoff state - Will-call readiness report Acceptance: Open the will-call board on mobile with no horizontal overflow and readable pickup states. ## Timeline - Kickoff (Week 1): Branch operations lead. Buyer action: Branch operations lead: approves the pilot offer, success criteria, and weekly launch decisions. Deliverable: map SKU, bin, will-call, receiving, and role vocabulary. Exit: SKU import and scanner test script approved. - Configuration (Weeks 2-3): Implementation lead. Buyer action: Branch operations manager: provides source data, validates import exceptions, and confirms cutover readiness. Deliverable: load sample catalog and receiving records into the demo workspace. Exit: Branch lead can complete receiving and count scenarios with sample data. - Pilot (Weeks 4-5): Counter manager. Buyer action: Warehouse lead: tests the workflow against real records before broader rollout. Deliverable: simulate scanner receiving, variance approval, and will-call readiness updates. Exit: Variance export and will-call readiness report are accepted. ## Commercial Terms - Recommended tier: Branch inventory pilot. Buyer can provide item master, bin, supplier, receiving, and will-call exports for one branch and one pilot category. - Pilot setup: $22k-$40k. Brand tokens, branch roles, counter dashboard, bin lookup views, and scanner-friendly workspace shell. - Recurring support: $1k-$3.5k/month. Branch launch thread: Business days during pilot; Branch operations review: One 45-minute session per week - SKU and bin import: $7k-$12k. Map SKU, UPC, bin, on-hand, reorder, supplier, and unit fields for one branch and pilot category. - Receiving and cycle count workflows: $7k-$14k. Configure receiving variance review, scanner input, count board, exception handling, and manual ERP export. - Pilot hosting and scanner support: $1k-$3.5k/month. Hosting, import refresh support, scanner testing, branch review, and workflow adjustments during pilot. ## Buyer Commitments - 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. - One branch workflow kickoff, one field-map review, and one receiving/cycle-count simulation. before configuration begins. - Branch launch thread with Next business day response during setup. ## Assumptions - Data path: 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. - Identity model: Staff email login for the pilot branch, with optional SSO after ERP and directory ownership are confirmed. - Session model: Branch-scoped sessions with role claims for counter, warehouse, and manager actions. - Domain strategy: Use inventory.clientdomain.com or branch.clientdomain.com for production and keep plumbing-supply.ideas-realized.com as the demo subdomain. - Payment milestone: 45 percent due at signature for branch tenant setup and item master mapping. ## Out of Scope - No ERP writeback or replenishment automation in the base pilot. - No real-time supplier EDI until source formats and exception rules are approved. - Cycle count corrections remain review-only until branch leadership approves posting controls. - Do not promise ERP replacement or real-time inventory authority. - Do not enable automated stock adjustments without sign-off on posting rules. - Do not include multi-branch replenishment in the base pilot. - Deferred module: ERP replacement or ledger posting - Deferred module: Supplier EDI and automated purchase order submission - Deferred module: Multi-branch replenishment optimization ## 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. - Scan SKU into receiving session: Scanner history and PO receipt panel update; hardware test pending. - Resolve cycle count variance: Count task exposes expected, counted, variance, and adjustment status. - Confirm will-call readiness from counter view: Pickup board surfaces staged, picking, waiting, and customer-ready states. - 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. ## Risk Controls - Pilot risk control 1: Implementation lead; Do not let ERP posting, supplier EDI, or replenishment automation expand the first pilot before branch workflow value is proven. - Pilot risk control 2: Product engineer; No ERP writeback or replenishment automation in the base pilot. - Pilot risk control 3: Growth lead; No real-time supplier EDI until source formats and exception rules are approved. - ERP posting can turn a branch pilot into a high-risk integration project.: Implementation lead; Start with import/export and only promote posting after variance handling is accepted. - Barcode quality and SKU aliases can break counter trust quickly.: Branch operations lead; Run scanner acceptance tests with real labels before any live branch workflow. ## SEO/AEO Expansion - Plumbing supply inventory software: /industries/plumbing-supply-inventory-software - What software helps plumbing supply branches manage inventory? (SoftwareApplication) - How should receiving variances be handled before ERP posting? (HowTo) - Inventory overlay vs full ERP replacement - Scanner receiving software vs manual receiving sheets ## Next Steps - Approve Branch inventory pilot and confirm $22k-$40k setup band. - Send required assets: SKU and bin export, Receiving variance examples, ERP export boundary notes. - Schedule One branch workflow kickoff, one field-map review, and one receiving/cycle-count simulation.. - Choose launch domain: plumbing-supply.ideas-realized.com preview now, then plumbing-supply.ideas-realized.com for production. - Use Scan SKU into receiving session as the first go/no-go decision. ## 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.