Distributor demo storefront, built on the PIMento API Sign in
Product image
Product image Product image Product image Product image Product image Product image Product image Product image

Men's Flex Polo

POLO

$24.00 and up

Men's 100% polyester moisture wicking polo shirt with solid interlock knit. Features three button placket, flat knit collar and open cuff. Tear away label at back of neck. No exterior branding. On-site embroidery available. This shirt is available in a women's matching style.

Order

Size Select
L
Condition Used
New Used
Color Select
Grey

Clear selection

L · Grey · Short Sleve · Dy Fit
10054-L · Out of stock
$24.00

Specifications

Style Short Sleve
Material Dy Fit
Unit Each

Product information

Embroidery: Up to 8,500 stitches (+$10.00) Size: Small, Medium, Large, X-Large, 2X-Large, 3X-Large, 4X-Large, 5X-Large

Production Time: 1 to 30 working days

Packaging: Individual poly bags upon request.

API reads behind this page 1 over the wire, 7 from cache · 316 ms total · template: Default Promotional
Method Path Source Status Time
GET /slugs('polo-shirt') cache 1h — —
GET /products/1037?$expand=items,media,attributes,related,applications,fitment,tabs,documents,modifiers cache 1m — —
GET /v2/products/1037?$expand=pricing network 200 316 ms
GET /slugs('polo-shirt') asked twice — —
GET /me cache 30m — —
GET /items(…)/attributes ×12 cache 30m — —
GET /categories cache 15m — —

204 and 404 both mean “no rows” on this API — which of the two an endpoint uses is per-endpoint, and the client maps both to an empty result rather than an error. Collections come wrapped in an OData envelope and are capped at 100 rows per page.

Rows marked cache were answered from memory, and the time beside each is how long that kind of read is held; one marked asked twice is something this page had already read while rendering, so it cost nothing either way. Catalog reads are cached by rate of change rather than on one site-wide timer:

Pricing and stock are read live on every view — there is no setting that caches them. That is why a warm product page still makes exactly one request: everything else on it came from memory.

The catalog can also drop all of it at once rather than waiting for a tier to lapse, by calling POST /hooks/cache when it publishes.