Special Orders Portal Analysis
project
e911ed3c71907b0c
Normalized: special orders portal analysis
moreland_contracts
Entity Properties (gold project table)
project_id
e911ed3c71907b0c
name
Special Orders Portal Analysis
client_id
—
canonical_metadata
—
created_at
2026-05-02 02:29:59.020102+00:00
updated_at
2026-05-02 02:29:59.020102+00:00
status
—
billable
—
recurring
—
squad
—
qa_partner
—
project_manager
—
lead_dev
—
description
—
state
—
team_name
—
closedate
—
dealstage
—
deal_amount
—
contract_type
—
contract_hourly_rate
—
contract_estimated_hours
—
contract_total_fee
—
47%
Separation Confidence
How distinct this entity is from others. Higher means no close matches existed when it was created. Lower means a near-match was rejected just below the 80% threshold — worth reviewing.
Moderate — a somewhat similar entity exists
100%
Avg Match Confidence
The average confidence score across all active source mappings. Shows overall quality of linkage between source records and this canonical entity.
Strong source linkage
Source Mappings (1)
| Source | Source ID | Display Name | Confidence | Method | Status | Actions | |
|---|---|---|---|---|---|---|---|
| moreland_contracts | 30a6aed1d0e4a06ea94a85403ade233b | Special Orders Portal Analysis | 1.00 | fuzzy+embedding | Active |
|
|
|
Source Record
bronze_moreland_contracts_ma_project_contracts
file_hash
30a6aed1d0e4a06ea94a85403ade233b
file_name
Special_Orders_Portal_Analysis_Notes.docx
file_path
https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/_layouts/15/Doc.aspx?sourcedoc=%7B38D75C5F-8239-465E-85C2-C04D6F57E598%7D&file=Special_Orders_Portal_Analysis_Notes.docx&action=default&mobileredirect=true
company
Final Frontier Project
project_name
Special Orders Portal Analysis
contact_person
—
contract_type
—
hourly_rate
—
estimated_hours
—
total_fee_estimate
—
brief_project_description
Analysis of the two special order systems currently in operation: Dallas (ZPB) and Akron (KJO), focusing on a portal rewrite that combines their functionalities.
start_date
—
extracted_at
2026-07-02T02:19:16.043349+00:00
raw_text_preview
Special Orders Portal Analysis
Dallas (ZPB) and Akron (KJO) Systems
Prepared for: Final Frontier Project
Discovery Period Analysis
Target Deadline: August 2025
Analysis based on discovery meetings held November 10 and November 17, 2024
Executive Summary
This document provides a comprehensive analysis of the two special order systems currently in operation: Dallas (ZPB) and Akron (KJO). The customer has requested a portal rewrite that combines the functionality of both systems, with a target delivery date before August 2025.
The Parker Avery consulting team (Marty, Charlotte, Aaron, Clay, and Kathy) conducted discovery sessions to document current workflows, identify gaps, and establish requirements for the harmonized solution.
Key Findings
Dallas system uses single-use SKUs; Akron creates reusable SKUs enabling sales tracking and customer service replacements
Critical gap: Dallas has $90,000+ annually stuck in refund cycles due to inability to replace orders without full refund
Akron has catalog vendor capability (15-30 vendors) that Dallas lacks entirely
Dallas pending payment issue: Orders can get stuck forever with no notification or recovery path
Akron's knowledge base provides automation that reduces manual work over time through self-learning
Dallas (ZPB) Special Order System
Overview
The Dallas special order system is characterized by a simpler workflow requiring a smaller team, but with significant limitations in SKU reusability and order recovery.
Order Initiation Process
Customer comes into store requesting special order (different size, metal change, etc.)
Store associate uses Find Create Quote screen (also called Special Order NVC - purple screen in POS)
Screen shows basic availability: sizes, weeks to make, metal colors, available changes
If changes are outside standard range: store emails special order task team for cost/availability quote
Quotes valid for 8 days unless vendor specifies otherwise
Task team is corporate-based (remote), handles vendor
file_created_at
2026-01-27T05:19:53+00:00
file_modified_at
2026-01-28T17:39:11+00:00
created_by
Justin Wray
modified_by
Paul Franke
_dlt_meta
—
|
|||||||