← All customers

Feiji helps improve an OEM system and keep orders moving

A home-furnishings company uses Feiji to bring together order records, system code and logs. The team gets help analysing problems, adjusting software and verifying results across order handoffs, progress updates and customer data.

A home-furnishings company
Order coordination

1hour

Fastest typical turnaround · previously ~3 days

Solve concrete business problems in the existing OEM system

Furniture OEM operations connect brand customers with internal orders, production and fulfilment. Orders, processing files and package progress are spread across systems. Resubmitted orders, delayed updates and missing customer information require business and technical staff to work together. As orders continue to move, searching, checking files and confirming progress take substantial time and affect subsequent handoffs.

The company introduced Feiji to help its team improve the existing system. When business staff reported a problem, Feiji brought together order records, system code and logs to help clarify rules, locate causes, adjust programs and verify the results. Individual problems became reusable system improvements.

Challenges and approach

Challenge

Business problems require repeated handoffs. Order exceptions move through clarification, technical investigation, changes and verification, creating long waits.

Approach

Use project context to help analyse and change the system. Feiji organises the background, checks rules and assists development and verification.

Challenge

Progress checks consume business and engineering time. Package summaries and missing historical records force people to search across systems.

Approach

Repair summaries and restore progress records. Feiji helps identify causes and improve synchronisation so staff can see more complete progress information.

Challenge

Missing or incorrect customer data creates repeated checks. Store names and other fields must be traced back to their source, delaying handoffs.

Approach

Fix source mappings and historical issues together. Let the system handle cases with clear evidence, while people review the remaining exceptions.

Help analyse and change typical issues in as little as one hour

When a returned order was submitted again, the team had to decide whether to retain its original number and whether processing files needed to be sent again. Previously, business staff described the exception, then engineers searched orders, compared files and checked code. Missing information led to further exchanges. Different interpretations could mean repeated changes and delay the order's return to processing.

Feiji helped connect the specific order, processing files and system logic. The agreed rule was to retain the original order number and resend processing files only when their actual contents changed. Feiji then assisted with program changes and testing, with business and technical staff confirming the results before delivery. Analysis, modification and verification could move forward together.

For typical problems with clear rules and a defined impact, the time from feedback to verified completion fell from about three working days to as little as about one hour. Business staff spent less time waiting and explaining the same issue, while engineers could reach modification and verification sooner. Faster resolution reduced disruption to downstream work.

3D concept illustration of two processing files compared side by side with one changed area highlighted
Concept illustration: comparing processing-file contents helps the team clarify the rules for resubmitted orders.

Improve progress synchronisation and save about 1,800 staff-hours a month

Accurate progress depends on continuous synchronisation of package and warehouse information. When summary jobs timed out or package history was missing, business staff could not confirm progress directly. They asked engineers to search records and contacted other departments for confirmation. Repeated problems meant several people searching for the same information, increasing workload and slowing fulfilment decisions.

Feiji helped the team inspect package summary queries and processing rules and fix timeout issues. After authorisation and scope checks, the team restored 142,818 package records for 12,898 historical orders. Orders with unclear ownership were isolated for human confirmation. Existing business states and callback records were preserved, making progress checks more complete without treating missing records as completed physical work.

After improvement, business staff could directly access more complete progress information. Engineers spent less time searching logs, adding records and explaining results. Across order-rule changes, progress synchronisation and data cleanup, the team reduced investigation and checking effort by about 1,800 staff-hours per month, leaving more capacity for customer responses, complex issues and delivery.

3D concept illustration of packages paired with records and one separate record awaiting review
Concept illustration: package records are restored after authorisation and scope checks; unclear ownership remains for human review.

Use business context to reach a task resolution rate above 99%

After order collection, store names and other customer details are used in searches, exports and business handoffs. Incorrect mappings or missing values previously required staff to trace and correct each order. Fixing only the current order left the same problem able to recur, creating repeated work and carrying errors into later collaboration.

Feiji helped check customer source fields against system mappings, locate the store-name problem and repair the processing rules. Historical orders with source evidence were corrected together. In one operation, the team reviewed 262 orders, corrected 45 wrong store names and filled 217 missing values. Cases without clear evidence remained with people for confirmation, aligning historical cleanup with source-level improvements.

With Feiji assisting routine work, only around a dozen complex issues from more than 1,000 monthly tasks needed further manual analysis. The remaining tasks were completed after review, with a reported resolution rate above 99%. Business and technical staff could focus on unclear rules and complex cross-system relationships instead of repetitive searching, checking and data entry, improving response times and handoffs.

Turn specific fixes into capabilities the team can keep using

Working with Feiji, the company progressively turned problems in order connections, progress updates and customer data into system improvements. Business feedback could receive a faster response, and the resulting experience remained useful for later work. Future work can build on customer-rule changes and operational feedback to improve exception detection, data checks and progress tracking, supporting production handoffs and customer delivery.