Automatic Deletion of Productions Older Than 3 Years

To optimize platform performance and adhere to best data management practices, productions older than 3 years will now be automatically deleted. This deletion includes media files, thumbnails, styling data, and briefs, but preserves your catalog and inventory data.

Implementation Schedule

The automatic deletion will be effective starting February 1, 2026. The first deletions will occur starting April 1, 2026 for productions created before April 1, 2023. Alerts and notifications will be active from February 1, 2026, to allow you to anticipate and download the files you wish to keep.

Preventive Alert System

You are informed well in advance of any deletion:

• ‍Visual Alert: a message appears on each affected production from 2 years and 9 months, indicating the exact date of deletion.‍
• Monthly Email: administrators receive a summary on the 5th of each month of the productions that will soon be deleted, with direct access to download them if necessary.‍
• Dedicated Filters: quickly identify the affected productions and media via the See productions to be deleted soon filter available on the homepage and in the Media Library.

What is Preserved

Your catalog data and inventory data remain intact. A visual icon replaces the deleted files to maintain the traceability of your productions.

Learn more about the deletion rules and impacts.

Marketplace Module: Advanced Configuration for Automated Merchandising

The Connect MKP module is evolving to offer you more flexibility: you can now choose, category by category, whether you want to activate AI-driven automated merchandising or maintain complete manual control. This hybrid approach allows you to tailor the behavior of Grand Shooting to the specifics of each type of product.

How does it work?

For a dynamic category with automated merchandising:

• The categories in your specifications are identified by prefixed view codes dyn: (example: dyn:face, dyn:back)
• The expected order according to the available photos is visible in the description of each view as well as the associated template for each AI variable.
• (Optional) A dyn:default view allows forcing the application of merchandising on all subsequent views.
• Automatic view recognition must be activated in the Live and the different stages of Production
• Exports are configured with the {$view} variable in the renaming.

For a non-dynamic category without AI:

• The categories in your specifications have standard view codes (example: face, back)
• Fixed templates are checked for each view
• (Optional) A default view sets a default template for all subsequent views
• Automatic view recognition must be activated in the Live and the different stages of Production
• Exports are configured with the {$view} variable in the renaming.

Usage Examples

Dynamic Category: A fashion brand configures its category so that packshot photos are automatically placed in view 1 and model photos in view 2.

Non-Dynamic Category: A packaging brand configures its category so that the front view is always first, the back view second, without reorganization by AI.

API Documentation: Addition of the "formats" Attribute in Specifications

The documentation for the GET /specification/category endpoint has been updated to reflect the addition of the formats attribute in the view_types.

What's Changing

Each view (view_type) now returns a formats array containing all applicable templates, with their complete properties: dimensions, margins, background color, ICC profile, resolution, and border strategy.

This information allows you to precisely identify the expected formats for each view of a category, thus facilitating the integration and approval of your exports.

API Improvement: Precise Control Over File Association

The POST /upload/url endpoint of the Grand Shooting API has evolved to offer you complete control over the organization of your files during import. You can now force the association between raw and retouched files, regardless of the file naming.

New Features

• ‍Forced Reference and View Association: directly define during the upload the product reference (ref) and the view type code (view_type_code) for each image, without relying on automatic recognition based on the file name.‍
• Parent Link Between Phases: explicitly associate a retouched photo with its original raw photo using the parent_id parameter, thus ensuring the alignment of images between the Live phase and the retouching phase, regardless of the view code.

How Does It Work?

Three new optional parameters are available in the POST /upload/url request:

• ‍ref : forces the product reference of the image (stored in merch_ref)‍
• view_type_code : forces the view code of the image (stored in merch_view_type_code)‍
• parent_id : forces the association with the parent image from the previous bench

When these parameters are specified, they take precedence over automatic recognition and are retained even in case of recalculation or subsequent reupload.

For more information: API Documentation

Fixes

• API: The API call DELETE /reference/{reference_id} has been fixed.
• Zip file downloads: The download of files has been optimized for dedicated environments to no longer stall during large downloads.
• AI: Optimization of AI processing and performance improvements.