--- title: "07th January 2026" slug: "release-notes7th-jan" updated: 2026-01-22T09:14:24Z published: 2026-01-22T09:14:24Z canonical: "pccdocs.bluemeteor.com/release-notes7th-jan" --- > ## Documentation Index > Fetch the complete documentation index at: https://pccdocs.bluemeteor.com/llms.txt > Use this file to discover all available pages before exploring further. # 07th January 2026 ### ![Two glowing star shapes on a gradient background, creating a vibrant visual effect.](https://cdn.document360.io/a899ba09-fd60-4d47-8b32-aabf7b60a39a/Images/Documentation/ChatGPT Image Aug 14, 2025, 07_12_51 PM.png?sv=2026-02-06&spr=https&st=2026-11-09T15%3A01%3A56Z&se=2026-11-09T16%3A01%3A56Z&sr=c&sp=r&sig=bRbMXlXpXb%2B66WsTUYZNtv3MjCiFsuZs2u8lIzddIrg%3D)**List of Features** | **No.** | **Feature** | **Description** | | --- | --- | --- | | **1.** | Enhanced SKU Journey Visibility for Distributors | To improve the visibility for distributors the following tabs are introduced in the SKU Journey screen: - A new SKU Journey status, **“Queued for Onboarding,”** has been introduced after the **Ready to Onboard** stage to clearly indicate that a SKU has been sent for onboarding. - A new **Rejected** tab has been added alongside the **Approved** tab, displaying all rejected SKUs under a dedicated chevron section. These enhancements improve transparency and usability for distributor users by providing clearer status tracking, easier identification of rejected SKUs, and better overall visibility into the onboarding lifecycle. | | **2.** | Supplier-Controlled SKU Deletion | Suppliers can now delete SKUs that have never been pushed to the Distributor Catalog. The system validates SKU history before deletion: - - If the SKU has **not** been sent to distributor catalog, deletion is allowed. - If the SKU **has** been processed, deletion is blocked and a message is shown: *“This SKU has already been processed and cannot be deleted.”* The **Delete** action is enabled only for eligible SKUs and disabled otherwise. This enhancement gives suppliers greater control and flexibility to manage SKUs while protecting data integrity in the Supplier Portal. | | **3.** | Distributor Control Over Supplier Import Options | Distributors can now centrally **disable any import options** across the Supplier Portal. When disabled, these options are restricted throughout the Supplier experience, including both legacy and new Syndication workflows, and is applied to **all suppliers associated with the distributor**. This enhancement gives distributors greater control over supplier onboarding methods, ensures consistent policy enforcement, and helps align import workflows with distributor-specific requirements. | | **4.** | Enhanced AI Prompting for Option 3 Attribute Mapping | The AI-driven attribute mapping for **Option 3** has been enhanced to improve accuracy, confidence scoring, and reasoning transparency. **What’s Improved:** - **Smarter AI Prompts:** The AI prompt now leverages known target attributes (template fields) along with their **attribute descriptions** to better understand intent and context. - **Improved Confidence Scoring:** Scoring logic has been refined with grounded, traceable rules, including clear incentives and penalties based on different mapping scenarios. - **Better Handling of Ambiguity:** Ambiguous mappings are now scored more appropriately, improving trust and usability. - **Enhanced Variant Mapping Coverage:** Stronger reasoning improves mapping accuracy across product variants. These enhancements lead to more accurate attribute mappings, clearer confidence scores, and improved transparency in AI decision-making resulting in higher-quality mappings and reduced manual intervention. | ### ![](https://cdn.document360.io/a899ba09-fd60-4d47-8b32-aabf7b60a39a/Images/Documentation/image(232).png?sv=2026-02-06&spr=https&st=2026-11-09T15%3A01%3A56Z&se=2026-11-09T16%3A01%3A56Z&sr=c&sp=r&sig=bRbMXlXpXb%2B66WsTUYZNtv3MjCiFsuZs2u8lIzddIrg%3D) **List of Bug Fixes** | **No.** | **Module** | **Bug Fixes** | | --- | --- | --- | | **1.** | SP | Selecting and saving a UoM from the secondary UoM list causes the newly added UoM row to disappear, and sorting within the cell text does not work. | | **2.** | SP | Importing a template with a valid UoM value (e.g., “$125” for an attribute limited to Dollar) is incorrectly flagged as invalid data. | | **3.** | SP | Take-back requests raised by suppliers do not appear enabled on the distributor’s SKU Journey screen, even though the request status is correctly set to “Initiated” in the payload. | | **4.** | SP | Publishing a copied template fails by prompting for node mapping rules, but the Node Mapping page does not appear, blocking template publication. | | **5.** | SP | SKU count parameter names in the API response contain spaces and do not follow standard naming conventions in Option 4 API response. | | **6.** | PCC | SKU changes are missing in the Audit Trail because the Audit Service expects a numeric customer taxonomy id, but a string value was being passed. | | **7.** | SP | Users cannot delete multiple draft templates sequentially; deletion fails after the first template. |