The item data analyst
Data accuracy & submission
- Works across thousands of item records
- Needs fast validation and bulk editing
- Owns data exceptions and resubmissions
“Show me what’s wrong, why it matters and how to fix it.”
bSync
From data mismatches to retail readiness.
A retailer data sync and compliance platform that helps CPG suppliers catch errors before they become rejected orders.
Success Metrics
Better data. Measurable business impact.
70%
Order rejections In the first year for one global supplier.
+50%
Operational improvement In one supplier’s Walmart data sync.
$50M
Increase in sales
Across several categories for one supplier.
Results reported for individual suppliers using the bSync platform. They are not attributable to design alone.
STAR Case Study
The project in one story.
S
Situation
Suppliers lost sales and margin when data mismatches caused rejected orders, penalties and payment deductions. Teams discovered problems too late.
T
Task
Create one trustworthy experience that validates data before submission, explains exceptions and helps every role take the right action.
A
Action
Map the order-to-cash journey, explore user needs, define the information architecture, prototype key workflows and iterate through usability testing.
R
Result
A unified design concept connecting item records, retailer rules, exception resolution and deduction tracing, shifting the focus from reaction to prevention. Individual suppliers reported fewer order rejections and improved data-sync accuracy after adopting the platform.
01 · The problem
A small data mismatch. A costly chain reaction.
Supplier and retailer systems don’t always agree. When discrepancies are found only after an order is submitted,the cost goes far beyond correcting a field.
Where product data lives today
ERP systems
Spreadsheets
Retailer portals
Email threads
Product catalogs
Price lists
Compliance rules
Finance reports
Before · Reactive
Find out after the rejection.
Scattered records, manual checks, unclear errors and costly deductions. Every exception becomes another fire drill.
After · Preventive
Know before the order ships.
One validated item record, clear retailer rules and actionable fixes — with an owner and an audit trail.
02 · Why this project
Getting on the shelf should not be the hard part.
Months of work go into getting a product retail-ready. Then an incorrect dimension, an outdated price or a missing field can stop the shipment and trigger a penalty.
The opportunity wasn’t another reporting tool.
It was a connected workflow that prevents errors at the source. Give analysts a clear fix, account managers an early view of risk, and finance a traceable path from a deduction to its data cause.
03 · Research approach
Before designing the interface, understand the work behind the data.
The proposed research approach examines the workarounds, handoffs and invisible expertise that keep supplier operations moving.
01Stakeholder interviews
02Contextual shadowing
03User surveys
04Competitive audit
05Support-ticket review
06Card sorting
07Journey mapping
08Moderated usability tests
04 · Competitive landscape
Existing tools solved pieces of the problem.
Each system had its strengths. The opportunity was to connect product information, retailer requirements and corrective action in one place.
| Existing approach | Strength | Opportunity |
|---|---|---|
| Retailer portals | Authoritative retailer requirements | One retailer at a time; fragmented workflows |
| Product information tools | Strong product data models | Not designed around retailer compliance |
| BI dashboards | Visibility and historical reporting | Reactive rather than preventive |
| Spreadsheets & email | Flexible and familiar | No automated validation or reliable audit trail |
Opportunity identified
Unify item data + retailer rules + pre-submission validation + clear exception resolution.
05 · Key design principles
From complexity to quiet confidence.
01
Prevent
Catch mismatches before submission, not after rejection.
02
Explain
Show the field, the rule and the next best action.
03
Prioritize
Make urgent exceptions visible without creating alarm.
04
Familiarize
Use spreadsheet-like patterns for high-volume data work.
05
Connect
Trace each item across retailers, orders and deductions.
06
Empower
Make ownership, permissions and every change transparent.
06 · Context & target users
One shared truth. Three different perspectives.
Designed for supplier teams working with large datasets, complex retailer rules and a common need for speed, accuracy and traceability.
The key account manager
Retailer relationships & readiness
- Coordinates retailer-specific requirements
- Needs early visibility into submission risk
- Keeps product launches moving
“I need to know we’re ready before the retailer places an order.”
The finance analyst
Deductions & reconciliation
- Investigates penalties and deductions
- Needs an end-to-end audit trail
- Connects payment issues to data causes
“Help me trace the deduction back to what actually happened.”
07 · Problem insights
Four gaps shaped the design direction.
Too many sources of truth
Teams reconcile the same records across spreadsheets, portals and internal systems.
Errors surface too late
Mismatches are discovered after rejection, when the cost of correction is already high.
Alerts lack a clear fix
An error code adds work when it does not explain the field, rule or next action.
Expertise becomes a bottleneck
Retailer-specific knowledge lives with individuals rather than in a shared, reliable system.
08 · User journey
From reactive firefighting to preventive control.
A connected path from preparing product data to reconciling payment — with a clear next step at every stage.
09 · Information architecture
A complex ecosystem. A predictable structure.
Five core destinations organize the supplier’s work, with shared item records connecting the whole experience.
10 · Core user flow
Every exception should end with a clear next step.
Validation is not a dead end. It connects the issue to a rule, a fix and a confident resubmission.
1Select retailer
2Validate data
3Review exceptions
4Edit or bulk fix
5Preview changes
6Revalidate & submit
11 · The solution
Wireframes
High-Fidelity Mockups
Meet bSync. One connected view of retail readiness.
A calm, focused workspace that makes risk visible and turns dense product data into clear, actionable decisions.
13 — Guided Exceptions
Less guessing. More guided fixes.
Users ignore error codes that don’t say what to do. bSync explains each exception in the context of the retailer’s rule and the item’s own data.
Specific — Shows the field, the value and the retailer rule that was triggered
Early — Flags mismatches before submission, not after rejection
Transparent — Explains why an item was flagged
Actionable — Offers a suggested fix with a before-and-after preview
14 — Design System
Precision with warmth. Consistency at scale.
A restrained neutral foundation, one electric-blue accent and semantic status colors — supporting dense information without adding visual noise.
Core palette
Electric blue
#2563EB
Primary actions, links and highlights.
Paper white
#FFFFFF
Clean backgrounds for content and layouts.
Surface
#F3F6FB
Cards, panels and secondary sections.
Ink
#0F1D3C
Headings and primary text.
Typography · Inter
Aa Bb 0123
One family. Clear hierarchy. Comfortable reading and compact data views.
H1
32 / Bold
Quick fox
H2
24 / Semibold
Quick fox
H3
20 / Semibold
Quick fox
Body
16 / Regular
The quick brown fox
Caption
14 / Regular
The quick brown fox
Label
12 / Medium
Quick brown fox
Accessible by intention
WCAG 2.2 AA is the design target: readable contrast, visible focus, and status communicated through text and icons.
Trust through transparency
Explicit role-based permissions and an item-level audit trail are core product requirements.
Built for real data work
A 12-column layout, reusable patterns and density options support large datasets and distributed teams.
15 — Accessibility, Ethics & Privacy
Designing responsibly for business-critical data.
Retail compliance data carries real financial consequences. These were treated as design inputs, not compliance checkboxes.
Accessibility
- Maintain WCAG 2.2 AA-oriented color contrast and visible keyboard focus states.
- Support keyboard navigation across data grids, filters, tabs, and bulk actions.
- Use plain-language validation messages that explain the issue and recommended fix.
- Communicate status through text labels and icons, not color alone.
- Provide screen-reader labels and accessible announcements for dynamic updates.
Ethics & Responsible Design
- Explain why an item is flagged and which retailer rule was triggered.
- Present suggested fixes transparently instead of silently changing business-critical data.
- Require users to review and confirm bulk changes using a before-and-after comparison.
- Make exception ownership and status clear to reduce ambiguity and operational stress.
- Preserve an audit trail so changes and decisions can be traced.
Privacy & Data Protection
- Apply role-based access so users can access only the information and actions appropriate to their responsibilities.
- Keep audit records of important data changes and user actions.
- Make permissions and access boundaries explicit.
- Follow data minimization and retention principles appropriate to business requirements.
- Consider applicable privacy obligations, including GDPR where relevant, and enterprise security requirements.
Project Impact
From firefighting to prevention.
Before
- Manual data reconciliation
- Late error detection
- Unclear error messages
- Fragmented ownership
- Limited traceability
After
- Centralized item data
- Pre-submission validation
- Actionable exceptions
- Clear ownership and actions
- End-to-end traceability
18 — Reflection
The best fix is the error that never happens.
This project frames compliance as a design problem, not just a rules problem. The experience should help people act earlier, understand the consequences and trust the system.
What this direction makes possible
Less manual reconciliation. Clearer ownership. Fewer avoidable handoffs. A connected view that gives analysts, account teams and finance a common language.
What comes next
Confirm actual project dates and contributions, validate the proposed workflows with supplier teams, and establish baselines for rejection rate, resolution time and deduction value.