Client: NordSupply · E-Commerce & Retail · Swedish B2B wholesaler (110 staff)
Fixing Supplier Feed Failures for B2B Wholesale
TechSupport Team maintained NordSupply’s B2B ordering platform, which used PHP, MySQL and SAP integrations. Over four months, client Jira records show failed supplier syncs falling from 14 to 1 per week. Order errors fell from 3.8% to 0.6% in Sentry.
Client and engagement facts
- Client
- NordSupply
- Industry
- E-Commerce & Retail
- Business context
- Swedish B2B wholesaler (110 staff)
- Delivery model
- Software maintenance
- Application
- B2B ordering with 40 supplier integrations
- Supplied geography
- Swedish
- Company size in source
- 110 staff
Related services: Software maintenance
Application stack and tools
Application stack
- PHP
- MySQL
- SAP integrations
- AWS
Tools used
- Jira
- Sentry
Why Support Was Needed
A supplier loaded a full catalogue refresh when a scheduled report held a database lock. This repeated until the team mapped the batch schedule and could see both jobs on the same timeline.
Technical Work
- Identified the schedule collision between the catalog refresh and the report.
- Fixed the schedule and added a retry guard on the affected feed.
- Documented every feed in Jira with owner and monitoring.
Representative Incident
The first retry implementation collided with the SAP vendor’s timeout. The engineers changed it to three retries with backoff so the two systems could complete their work.
Use the order flow failure map to find the last confirmed state, then record recovery decisions in the failed order replay worksheet.
Results and how they were measured
| Metric | Baseline | Result | Units | Measurement window | Source and scope |
|---|---|---|---|---|---|
| Failed syncs | 14/wk | 1/wk | /wk | 4 months | Client Jira |
| Order errors | 3.8% | 0.6% | % | 4 months | Client Sentry |
| Batch overrun | 2.1 h | 20 min | Baseline: h; Result: min | 4 months | Client Jira |
Evidence and Limitations
The four-month comparison excludes one SAP vendor outage. The team recorded owners and monitoring for all 40 supplier integrations.
Supplier Integration Inventory
The engineers documented all 40 integrations and repaired similar issues on 12 other feeds.
Scope a Similar Engagement
Send a brief on your ERP, feeds and the batch jobs that delay orders or require manual recovery. Request a support plan or explore software maintenance.
Get a technical support plan
Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.
- We reply by email.
- We agree a call about the roles, your stack and the hours.
- If there is a fit, we propose engineers after an assessment.