Travel-product platform+ SHINCHUK
Product name, destination image, and URL. One listing for the search channel.
Making an impact in everyday work
We connected travel-product data with image folders to produce channel-specific EP feeds. Missing images, duplicate URLs, and format errors were separated for review.
What changed in this workflow
- 10,000 per month
- 5 min per item → Approx. 2 min per item
- Approx. 500 hours per month
- Repeated product entry and image selection became bulk generation followed by targeted exception review.
Time savings are calculated from volume and the change in time per item, based on the implementation and validation records in the existing casebook.
An anonymized implementation story, including work completed by the SHINCHUK team in previous organizations and projects.
Every row of product data meant another image to find.
Publishing travel products to a search channel required formatting data as an EP feed: a file carrying product names, URLs, and other listing information. Owners copied Excel values and searched folders for images matching each product and destination.
At 10,000 items a month, data entry and image selection repeated constantly. Beyond generating files, owners had to find missing images, duplicate URLs, and non-compliant fields. Handling product data, images, and uploads separately added work.
We linked image candidates by product name and destination and generated names and URLs under channel rules. File generation also produced a review list, separating bulk production from exception checks.
Connect data and images. Produce uploads and review lists.
Review product data
We read product spreadsheets and checked each channel's required fields, preparing the values needed for the final EP file.
Product data to format under channel rules
Connect image candidates
We found destination images using product names and destinations, incorporating folder searches into product-data processing.
Image candidates by product
Generate names, URLs, and files
We generated names and URLs for the search channel and prepared compliant EP feeds and product images, applying consistent rules at scale.
Channel EP feed · Product images
Separate exceptions
The source records and review results are attached to this handoff.
Missing images, duplicate URLs, and format errors were listed for review. Owners checked those items instead of recreating every product.
Image, URL, and format review list
Keep review items visible after bulk production
File generation and exception checks were built together. Upload outputs and review lists remained separate, so file count alone did not define completion.
Repeated product entry and image selection became bulk generation followed by targeted exception review.
What the team can use
- EP feedA file containing product names, URLs, and listing information for the search channel
- Product imagesImages matched and prepared by product name and destination
- Exception review listA list distinguishing missing images, duplicate URLs, and channel-format errors
System handlesConnect products and images · Generate channel filesOwner reviewsCheck missing images, duplicate URLs, and format errors