Product Update 26th Feb'26
🔒Amazon SP-API fees: action needed to avoid disruption (free option available)
Amazon has announced new fees for third-party developers using SP-API. This is an Amazon-driven policy change, and it impacts the shared public app many of you use today to connect merchant Amazon FBA stores to Ignite.
What’s changing
Jan 31, 2026: $1,400 annual subscription fee for third-party app developers
Apr 30, 2026: usage-based monthly fees for SP-API GET requests (tiered by call volume)
Amazon announcement: https://developer.amazonservices.com/spp-announcement
Your options:
✅ Option 1 (Recommended): Switch to a Private App (FREE)
Have each merchant authorize Ignite as a developer directly via their own Seller Central account.
One-time Seller Central authorization per merchant
All workflows continue as-is
Includes a one-time complimentary training for your team to migrate existing merchants and onboard new ones
If you ever want us to handle merchant-by-merchant migration later: $100 one-time per merchant
📌 Option 2: Stay on the Public App ($50 per seller store per month)
$50 per connected Seller Central store per month
Billing starts: Mar 31, 2026
If you have 50+ stores, reach out for volume pricing
What we need from you
Please reply by Mar 15, 2026 with your choice. If we do not hear back, we will keep you on the Public App to avoid service interruption and billing will begin on Mar 31, 2026.
🚚 Proglo Shipping is now live in Ignite
Following up on last month’s shipping partner announcement, Ignite is now integrated with Proglo Shipping. You can connect it from the Connections module to access highly competitive rates, especially for USPS, when purchasing labels for DTC and FBA shipments.
If you would like Proglo enabled for your account, please reply to this email and we will help you get it set up.
📦 Inner packaging materials are now live in Ignite
You can now create inner packaging materials (inserts, inner bags, wrap, filler, thank-you cards, etc.) as structured master data inside Ignite. This standardizes what your packers use on the floor and gives you a consistent way to capture inner packing usage during fulfillment, instead of relying on memory or informal SOPs.
🏷️ Set default inner packaging materials for SKU
For SKUs that require the same inner packaging every time, you can now define SKU-level defaults. When the order hits packing, Ignite automatically pre-loads the recommended inner packaging for that SKU, reducing missed inserts and eliminating repetitive manual selection for packers.
📥 Bulk upload SKU default inner packaging configs
If you have a large catalog, you no longer have to configure defaults one SKU at a time. Ignite now supports bulk upload of SKU-to-inner-packaging defaults using a template flow, with validations to catch mapping issues early. This makes it practical to roll out standardized packing rules across hundreds or thousands of SKUs quickly.
⚡ Defaults now flow into packing, with easy pack-time adjustments
During packing, Ignite now surfaces pre-selected inner packaging materials based on the SKU defaults, so the pack step stays fast and consistent. Packers can also add or adjust inner packaging materials at pack time when exceptions occur, so you keep both speed and accuracy without breaking the workflow.