Datta Vellal
Back

25 May 2016Amazon IndiaProject

Turned catalog feed migration into a self-service procedure used for 29 providers

I built a consistent XML-to-JSON parser, wrote the migration procedure with the support team and took myself out of the approval path; 29 feed providers moved onto it without a developer involved.

  • Catalog
  • Delivery
  • Quality

29

feed providers migrated

self-service, without engineer involvement

~10%

less transformation code

about 600 to about 550 lines for one standard, per a support engineer

Without it
Inconsistent parser output kept blocking search indexing, and every feed migration waited on a developer.
The call
Fix the parser once, then give the support engineers a procedure they could run without me as approver.
What I did
Designed and coded the parser and a bulk migrator, walked the support team through the procedure, and built their feedback into the guide.
What changed
29 providers migrated without developer involvement, and support engineers reported shorter, more readable transformation code.

What people said

“TL;DR The new parser implementation rocks and code is more readable and easy to understand !!”

Application Engineer, catalog support teamAmazon, 2016

“The wiki contains most of the steps on clear cut to complete the migration of a standard from old XML to NEW parser and that helped eliminating the Dev hand hold on migration.”

Engineer, catalog support teamAmazon, 2016