Feature Requests

Under Consideration

Planned

Building Now

Released

Feature Request

Currently, clients must manually contact customer support to cancel subscriptions or update their credit card details, even though Skulytics operates on a subscription-based pricing model. This creates unnecessary support requests and inefficiencies.The goal is to create a new “Billing Information” page within the Customer Portal that allows clients to directly manage their payment details via the Stripe portal, without contacting support.This will streamline billing management and improve the overall client experience.

Under Review

Add Billing Information Page to Customer Portal

Raihan Ayita Putri

Feedback from : Chris J For brands that do not have manufacturer rebates available from Nationwide or NECO, periodically check their official websites for any updated rebate information. This is not a high-priority task, but a nice-to-have to help ensure we capture all available rebates across brands.

Regularly Check Brand Websites for Manufacturer Rebates (Nationwide / NECO Not Available)

we should add notifications settings to the Skulytics user portal so that our clients can pick which notifications they want to receive.<ul><li>all notifications</li><li>Appliances</li><li>Furniture</li><li>Mattresses</li><li>Buyback</li><li>(add new categories as they become available)</li></ul>

Add Client Notification Settings to the User Portal

chris_johnson

<ul><li>Old LAP prices need to be removed as soon as we find out that there is an issue with scraping a competitors LAP prices.<ul><li>keeping old data risks us not being accurate when we are unable to scrape for updated data</li></ul></li><li>We should also send out notifications in the user portal (and changelog for <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Appliance.io">Appliance.io</a> and other platforms?) about the specific competitor LAP prices being down/unavailable/delayed/fixed</li></ul>

Procedure for when we have LAP scraping issues

Currently, there is no separate endpoint for type relations, as it is still included in the “get a product” endpoint. We need to create a dedicated endpoint to make it easier to read and map the data, which could also potentially increase our hit count.

Add new endpoint (Type Relations)

developer_data

Hello,Sorry for all of the variation questions. I have put them all into one email now. You can delete the previous emails.I am using this API to test right now: Serta: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://api.skulytics.io/v2/e-commerce/product?product_type=furniture,mattresses&amp;brand=Serta&amp;status=Active&amp;per_page=100&amp;page={page_num}">https://api.skulytics.io/v2/e-commerce/product?product_type=furniture,mattresses&amp;brand=Serta&amp;status=Active&amp;per_page=100&amp;page={page_num}</a>1 - See the sample data attached that we use for testing and development. The variations format is perfect here. Is it possible within the API to match this type of variation structure? I believe this would be best for the end user to utilize.<file-preview-component data-featurebase-content-filename="sample-data.rtf" data-featurebase-content-filesize="22372" data-featurebase-content-filetype="text/rtf" data-featurebase-content-key="68b7b0d7acd73d73c464e52d/post/68d4e60e507deeb4a2471fd5/01997fa2-90d4-719e-8b82-bad6ab337ca2/b64u-c2FtcGxlLWRhdGEucnRm.rtf" src="https://68b7b0d7acd73d73c464e52d.featurebase-attachments.com/c/post/68d4e60e507deeb4a2471fd5/01997fa2-90d4-719e-8b82-bad6ab337ca2/b64u-c2FtcGxlLWRhdGEucnRm.rtf?X-Amz-Expires=3600&amp;X-Amz-Date=20260227T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260227%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=9d2e5cca45f3c5402e0fb4a8f95935924b03847de664a045a235cad0a6466db6"></file-preview-component>

Add Variations and Attributes Data Point for Furniture and Mattresses

Use the Ashly API as a role model for this. Add country codes to set us up for international expansion in the future. So if the user is accessing US data through the API, they need to call the US code.

Completed

High Priority

Add country codes to API to prepare for International expansion

Jon Slyman

Hi team, We have feedback from cellsoq add for add this items to our catalog. OnePlus 15, OnePlus 15R, OnePlus 13

Add OnePlus 15 Series and 13 Series

Reusely Buyback

1.) Under the” Smart Rings” category.2.) Add Brand as “Oura”.3.) Add these as Model under Oura:<ul><li>Oura Ring 4 Ceramic</li><li>Oura Ring 4</li><li>Oura Ring 3</li><li>Oura Ring 2</li></ul>ExampleSmart Rings &gt; Oura &gt; Oura Ring 4 Ceramic. Please let me know if there is any better suggestion.Link from buyback word: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.buybackworld.com/sell/wearable-tech/oura">https://www.buybackworld.com/sell/wearable-tech/oura</a>Link from Oura: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://ouraring.com/store">https://ouraring.com/store</a> Note: our current category is called " Smart Ring"- we need to change it to "Smart Rings". Note: Requested by Eden from RT.

Add Oura rings under "Smart Rings" Category.

sayed

(Request made by Jos from KE). Please let Sayed know when request is complete. <file-preview-component data-featurebase-content-filename="Reusely product export_28-11-2025.xlsx" data-featurebase-content-filesize="12786" data-featurebase-content-filetype="application/vnd.openxmlformats-officedocument.spreadsheetml.sheet" data-featurebase-content-key="68b7b0d7acd73d73c464e52d/post/6929b2e9896a0374327c2889/019acae2-bfb5-730c-bd9b-3bb040c2d0b1/b64u-UmV1c2VseSBwcm9kdWN0IGV4cG9ydF8yOC0xMS0yMDI1Lnhsc3g.xlsx" src="https://68b7b0d7acd73d73c464e52d.featurebase-attachments.com/c/post/6929b2e9896a0374327c2889/019acae2-bfb5-730c-bd9b-3bb040c2d0b1/b64u-UmV1c2VseSBwcm9kdWN0IGV4cG9ydF8yOC0xMS0yMDI1Lnhsc3g.xlsx?X-Amz-Expires=3600&amp;X-Amz-Date=20260227T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260227%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=0730400c55f32a018f3cf9e8b3366ebed865886130c3f913aef76d15f6e2b933"></file-preview-component>

Add these items to catalog.

Developer Data

We are currently working on the input and optimization of Nintendo Accessories/controllers in our catalog. We have encountered the following points which we would like to adjust to ensure a correct and differentiated product presentation:1. Differentiation of Wii Consoles and Controllers Currently, the Wii consoles under the "Game System - Nintendo" category are often displayed with a bundled remote control (Wii Remote) in the product image.Request: We kindly ask that the product display be adjusted so that the following items are displayed separately and as standalone products in the catalog:The Wii Console (the main system)The Wii Remote/controller (the accessory) – Displayed under the controllers category.The Wii Nunchuck (the accessory) – Also displayed separately and as a standalone product under the controllers category.2. Display of Standalone Chargers We also want to be able to offer and correctly display standalone chargers.Request: Is it technically possible to input and display the following standalone chargers as separate products?Standalone Nintendo DS ChargerStandalone Nintendo 3DS/DSi Charger

Request from Reusely

Feedback from : Kevin Description: Identify and fix duplicate product names under the same brand for furniture and mattress data. If multiple SKUs share the same name, append “ - Color” to the product name to make each SKU unique. Ensure all updates are reflected correctly in Public API.

Fix Duplicate Product Names in Furniture and Mattress Data

Why are we not using google auto complete here. I need to manually type in my address.<img data-width="100%" data-align="left" data-featurebase-content-key="68b7b0d7acd73d73c464e52d/post/69005c0ee7beafebb25f278d/019a2999-3224-7e47-a1b7-7c7ea0bcca4b/b64u-c3MtMDE5YTI5NjctOTdjYi03ZTA5LTg0YTQtMDhlNGNmMjFkYmFjLnBuZz9YLUFteg.png" data-featurebase-content-filename="ss-019a2967-97cb-7e09-84a4-08e4cf21dbac.png?X-Amz" src="https://68b7b0d7acd73d73c464e52d.featurebase-attachments.com/c/post/69005c0ee7beafebb25f278d/019a2999-3224-7e47-a1b7-7c7ea0bcca4b/b64u-c3MtMDE5YTI5NjctOTdjYi03ZTA5LTg0YTQtMDhlNGNmMjFkYmFjLnBuZz9YLUFteg.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260227T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260227%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=8056e2aebd8f8cc4e0b4a3f482ecf8a35f66458e0ba488d41e2aede67bf2044e">

Google Adress complete

See updated attachment.<file-preview-component data-featurebase-content-filename="Skulytics Furniture &amp; Mattress Updates_Clean Up.docx" data-featurebase-content-filesize="17783" data-featurebase-content-filetype="application/vnd.openxmlformats-officedocument.wordprocessingml.document" data-featurebase-content-key="68b7b0d7acd73d73c464e52d/post/68ef0cdb5bb1739d16c1d3c4/0199e5c9-f8c5-78aa-bd15-506e7db9db23/b64u-U2t1bHl0aWNzIEZ1cm5pdHVyZSAmIE1hdHRyZXNzIFVwZGF0ZXNfQ2xlYW4gVXAuZG9jeA.docx" src="https://68b7b0d7acd73d73c464e52d.featurebase-attachments.com/c/post/68ef0cdb5bb1739d16c1d3c4/0199e5c9-f8c5-78aa-bd15-506e7db9db23/b64u-U2t1bHl0aWNzIEZ1cm5pdHVyZSAmIE1hdHRyZXNzIFVwZGF0ZXNfQ2xlYW4gVXAuZG9jeA.docx?X-Amz-Expires=3600&amp;X-Amz-Date=20260227T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260227%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=cb85b9b0a811717e7198b4eb9057abddacf7b7dd269c8cb2737c3535b3a0cf89"></file-preview-component>

Skulytics Furniture & Mattress Updates/Clean Up

The current <code>Update Pricing</code> feature updates <code>active_map</code> and <code>lrp</code> fields in <code>v4_product_data</code>, but it does not include updates to the <code>map</code> column. This omission causes data inconsistencies between displayed MAP values and the actual pricing structure used in the business logic. Root Cause Analysis (RCA)<ul><li>Existing SQL statement omitted the <code>map</code> column from the <code>SET</code> clause.</li><li>The original assumption that <code>active_map</code> always mirrors <code>map</code> is outdated. </li></ul><img data-width="100%" data-align="left" data-featurebase-content-key="68b7b0d7acd73d73c464e52d/post/68e484793013aae8c2a2b2b4/0199bc9b-7de5-7416-b4a9-8b1e341766fd/b64u-U2NyZWVuc2hvdCAyMDI1LTEwLTA3IGF0IDA5LjU4LjQzLnBuZw.png" src="https://68b7b0d7acd73d73c464e52d.featurebase-attachments.com/c/post/68e484793013aae8c2a2b2b4/0199bc9b-7de5-7416-b4a9-8b1e341766fd/b64u-U2NyZWVuc2hvdCAyMDI1LTEwLTA3IGF0IDA5LjU4LjQzLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260227T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260227%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=91e5d39d88cbc829318749ffabd43e28caacc51d3800b069a0ff80fe555d69e5" data-featurebase-content-filename="Screenshot 2025-10-07 at 09.58.43.png">

Improvement: Include MAP in Update Query Logic

As a platform, we need to see what clients are consuming what. Here is a video with more details: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.loom.com/share/a928001b002149feaa4ad44e4d21ae29?sid=09f0f227-50e5-4f6f-8351-491e46982c0a">https://www.loom.com/share/a928001b002149feaa4ad44e4d21ae29?sid=06396165-56f5-49c3-993f-6a1c6987e134</a>

Allow us to break down API usage per client/API KEY for platforms

Problem Retailers using <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://appliance.io">appliance.io</a> want to display manufacturer reviews on their product pages without relying on third-party embeds (e.g. Bazaarvoice). Skulytics does not currently expose manufacturer review data at the model level, limiting SEO and on-page trust.Request Add a Manufacturer Reviews API at the model level.API Behavior<ul><li>Input: Manufacturer + Model</li><li>Output:<ul><li>A render-ready review summary string</li><li>Structured review data for SEO (<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://schema.org">schema.org</a> compatible)</li></ul></li></ul>Example Response<pre><code>{ "manufacturer_reviews_text": "Rated 4.6 out of 5 stars based on 1,248 manufacturer reviews", "manufacturer_reviews": { "aggregate_rating": { "rating_value": 4.6, "review_count": 1248 } } } </code></pre>Requirements<ul><li>Reviews are manufacturer-provided, not retailer-generated</li><li>Data must support JSON-LD / Google rich results</li><li>If no reviews exist, return a clear “not available” state</li></ul>

Scoping

Manufacturer Reviews API (Bazaarvoice-style)

We need to make sure we are adding the matching dryers to washers and washers to dryers so that the matching model is always available in the package data. This will greatly help retailers and customers when trying to figure out which washer and dryer should be purchased together.As part of this task, we also need to start creating washer and dryer sets/package skus so retailers can show a laundry package (that has an image of the washer and dryer next to each other or stacked) and when added to cart it pulls in the individual skus that make up the package.types of packages:Side-By-Side Electric = Washer + Electric DryerSide-By-Side Gas = Washer + Gas DryerStacked Electric = Washer + Electric Dryer + stacking kitStacked Gas = Washer + Gas Dryer + stacking kitNote: We also need to make sure all laundry accessories are getting listed in accessories data<ul><li>washer fill hoses</li><li>dryer cords</li><li>venting kits</li><li>stacking kits</li><li>matching pedestals</li></ul>Examples:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.ajmadison.com/c/washer-and-dryer-sets/">https://www.ajmadison.com/c/washer-and-dryer-sets/</a>NOTE: IF ANY WASHER OR DRYER GETS DISCONTINUED, THEN ANY PACKAGE WITH THAT WASHER OR DRYER ALSO NEEDS TO BE DISCONTINUED.

Add Washer and Dryer Sets/Packages

We have clients in memorbilia that are moving more into trading cards. In addition, this is a rapidly growing category (particularly around Sports, Pokemon, Magic The Gathering)Clients have suggested <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.cardladder.com/">https://www.cardladder.com/</a> as the BEST source of data, but I also know of <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://pricecharting.com">pricecharting.com</a>. Would love an option in Reusely to offer this.

Trading Card (TCG) Data

Problem Currently, ADC data is provided in CSV format. The manual handling of CSV files is not scalable and creates inefficiencies for system integration. Goal Convert the existing ADC CSV data into a structured API format.Map all relevant CSV fields into the correct structure within the Skulytics system.Ensure data consistency and standardization across all fields.Implement proper API access control to ensure secure and restricted access.

Integrate ADC Data with API

Please update the page name from Monitoring Client to Client Usage to better reflect its actual function. The page primarily displays usage metrics for each Skulytics client, so the new name aligns more accurately with the content and purpose of the page.