Audience: Tech-CS triage / whoever is covering the role. Use this to route tickets to the right engineer.
Important: treat this as a guide, not a fixed rule. Engineer remits change, people move teams, cover for each other during leave, and occasionally a ticket gets reassigned because it turns out to be someone else's area. Always sanity-check against current reality, and when you are not sure, assign to the most likely owner and note in the ticket that it may need redirecting. This guide should be reviewed periodically.
Route by area, not just by name
The reliable way to route is by the area of the problem, then to the engineer who owns that area. The map below is organised that way.
Prodigi engineering
- Luke Barker , main API; SKU and lab configuration (OneFlow); print-file transforms (rotation, crop, split, scaling, enlargement); spine width/logic; books; pricing on products; authentication. The default owner for "correct file in, altered file out" print-placement issues and for "Invalid Attribute Value" OneFlow config gaps.
- Blas Gomez , Shopify, WooCommerce, Etsy, Rutter; sales-channel order sync and status write-back; imagery; Python. The default for sales-channel connection and sync issues.
- Anwen Govier , sales channels; dashboard; product catalogue and publishing; OAuth; WooCommerce. Covers sales-channel/dashboard issues (and has covered payments/PayPal work).
- Callum Coles , mockups and 3D; some product-data/recommended-dimensions issues.
- Jaimie Ouwerling , shipping and routing; tracking; pricing sheets; product and print-area data; recommended dimensions. Data Analyst in the Networks team. The default for shipping, tracking, and product-data issues.
- Mike Hole , senior back end; main API; OMS; AI.
- Steve Martin , senior back end; main API; OMS; pricing sheets and OneFlow. (Note: flag remits carefully, some pricing/API work has moved between Steve and Luke.)
Peecho engineering (NL-based, also work on Prodigi)
- Bianca Udrea , Peecho back end; also works on Prodigi; spine and book issues; tracking links.
- Konrad Gałązka , senior Peecho back end; likely owner of async endpoints and lower-level Peecho work.
- Stephan van Eijkelenburg , senior front end; can also do lab integrations.
Leadership / product / other
- Ed Parry , Head of Product and Platforms. Loop in for product-capability decisions and feature/UX questions (for example whether to build a bulk-configuration tool), not for bug fixes.
- Kate Farrell , Head of Operations.
- Tom Gallard , CTO.
- Hannah Davies , Head of Customer Services. Often the one flagging issues into Tech-CS and setting priority.
Quick routing by symptom
- Print file wrong (rotated / cropped / enlarged / split) → Luke
- "Invalid Attribute Value" at a lab / SKU not configured in OneFlow → Luke
- Spine dimensions / spine endpoint errors → Luke (Prodigi side) or Bianca (Peecho side)
- Shopify / Etsy / WooCommerce connection or sync issue → Blas
- Sales-channel OAuth / dashboard / catalogue → Anwen
- Shipping, tracking, routing, pricing sheets, recommended dimensions → Jaimie
- Mockups / 3D → Callum
- OMS order-state / status mismatch → Mike
- Peecho book / async / mapping → Bianca (may need Konrad)
- Amazon SP-API app / developer-account level → sales channel (Anwen) but flag it likely needs whoever administers the Amazon developer account
- Product-capability or feature decision → flag Ed
When to note "may need redirecting"
If an issue spans areas (for example a print-area problem that could be product data or file transform), assign to your best guess and say so in the ticket, naming the alternative owner. This is better than leaving it unassigned, and engineers will reassign if it is not theirs.