Seeing an unwanted error can be a bit of a head-scratcher.
We covers some common errors and how to tackle them. See through the relevant section, and if you're still stuck, our support team is always here to help via chat.
"Sorry, an error happened"
A general error that can pop up in various places like purchase orders (POs), draft orders, integrations, and during forecast updates.
It's often transient, so here are a few things to try first:
Force a Resync: Give Prediko a little nudge! Use the circular arrows icon in the left-hand menu to force a resync. Then, wait 15–20 minutes before trying again.
Browser Refresh: Sometimes your browser just needs a reset. Try refreshing your browser, clearing your cookies, or even trying a different browser or an incognito window.
Still Happening?: If the error keeps appearing, please take a screenshot and share it with our support team. It's super helpful if you can also note where in the app it occurred and what steps you took leading up to the error.
SKU Unavailable When Creating a PO or Draft Order
If you can't find a SKU when you're trying to create a PO or draft order, it usually means Prediko can't locate the SKU in the intended ordering location, or it hasn't fully synced yet. Let's run through these checks:
Force a Resync: Newly added or updated SKUs in Shopify might need a moment to appear in Prediko. Force a resync and wait 15–60 minutes before checking again. Prediko syncs from Shopify directly, but a manual nudge can speed things up.
Check "To Order" in the Buying Table: Head over to your Buying Table and make sure the SKU is set to Reorder = Yes. If it's not, it won't show up when creating POs.
Location in Shopify: Prediko needs the SKU to have inventory registered at the location in Shopify (even if the quantity is 0).
In Shopify, go to Products → Product → Variant → Inventory → Edit locations and confirm the location is added.
Location in Prediko: In Prediko, navigate to Settings → Locations and confirm the location isn't disabled. Disabled locations can't be used for creating POs.
Archived or Non-Physical Products: Just a heads-up, archived, digital, and non-physical products won't appear in Prediko. Learn more
Same SKU Mapping: If your SKU code appears on more than one product, go to Settings → Inventory Settings → Same SKU Mapping to ensure it's correctly mapped to the primary product you intend to use.
Important Note: SKUs must exist in Shopify before you can use them in Prediko. There isn't a way to add new SKUs directly within the Prediko app.
Errors When Importing Files (CSV / Excel)
Import errors usually appear in red on the validation screen and need to be resolved before you can proceed though you often have the option to skip problematic rows and import the rest.
Here are the most common culprits:
Mandatory Fields Empty: All columns marked with an asterisk (*) are essential and must be filled in.
Incorrect Formatting: Dates, numbers, and text need to be an exact match to the format shown in the template's instructions tab and any existing data in Prediko/Shopify.
SKU Not in Shopify: For PO or supplier-SKU imports, all SKUs must already exist in Shopify.
Wrong Header Row Selected: If you're not using a Prediko template, double-check that the correct header row is selected during the import flow.
Supplier Column: When updating costs, ensure you include the
Suppliercolumn in your import file.Suppliers First: If you're importing SKUs or POs that reference new suppliers, make sure you create those suppliers in Prediko first before importing.
Problematic Non-Mandatory Columns: Sometimes, a malformed value in a non-mandatory column (like "category") can cause issues. Try removing those columns if you're stuck.
Use Our Template: We highly recommend downloading the import template from Settings → Import and following the instructions tab carefully.
Please do not delete the pre-existing instruction rows at the top of the file.
If you're still seeing errors, please contact our support team via chat.
Errors When Syncing a PO to a 3PL (SKULabs, SKUSavvy, Deposco, ShipHero, etc.)
If you encounter an error when clicking "Create PO in Integration Partner," here are some key things to check:
Product and SKU Names Match: It's crucial that product and SKU names are identical between Prediko and the integration app. Any slight mismatch can cause issues.
Supplier Configuration: The supplier on your PO needs to be recognized and correctly configured in both Prediko and your integration app.
Location Exists in 3PL: The pickup or destination location for your PO must be configured and active in your 3PL's integration settings.
Integration Active: Double-check that your integration is still active and authorized by going to Settings → Integrations.
Re-import PO: Sometimes, re-importing the PO via CSV can resolve sync issues.
PO Status: Ensure the PO status in Prediko is set to Ordered after confirmation, so Prediko correctly treats the units as in-transit.
If the issue persists, please share the PO number and 3PL name with our support team.
An issue occurred during the Plan update
This error appears when Prediko can't complete a forecast recalculation, or sometimes when switching between planning models (e.g., Smart to Simple).
Wait and Retry: This can sometimes be a temporary glitch during a background sync. Wait a few minutes and try again.
Force Resync, Then Plan Refresh: Force a resync first (using the circular arrows), wait 15–20 minutes, and then trigger a plan refresh.
Adjust Your Plan Settings:
Switch to Manual: If you've made manual edits you want to preserve, consider switching your plan to
Manualtemporarily.Growth Target: Ensure your growth target accurately reflects your real Year-over-Year (YoY) expectations.
Trend Emphasis: Adjust the trend emphasis (e.g., 3 vs. 12 months) so that recent sales velocity is weighted appropriately for your planning needs.
Historical Data: If you suspect corrupted or outlier historical data (from migrations, promotions, or stockouts) is skewing your model, you might need to exclude those ranges from your plan baseline.
Persistent Issue: If the error continues over multiple days, please contact the support team – it may require a deeper investigation on our end.
Account already exists - Adding a Second Shopify Store
This message means the Shopify store you're attempting to connect has been previously linked to a Prediko account.
If it was connected to a different Prediko account, it will need to be disconnected from there first. Please contact our support team with the store URL, and they can help check the account status for you.
Other Common Scenarios & Troubleshooting Tips
Here are a few more situations you might encounter and how to handle them:
New Product Forecasting Problems
If your new product launches show very low or no recommendations, or sales aren't being counted for days, here’s what you can do:
Create as Draft: Create the product as a draft in Shopify, then use Prediko’s "Add Plan / Replan" feature to seed an initial forecast.
Smart Model / Manual Upload: Consider using the Smart model or a manual upload to set an initial forecast.
Shorter Trend Emphasis: For very recent momentum, using a shorter trend emphasis in your plan can help weigh recent velocity more properly.
In-Transit & Stock Not Updating
If incoming POs or transfers aren’t counted in forecasts (so your End-of-Month stock doesn't decrement correctly) or in-transit quantities show inconsistently:
Mark POs as Ordered: Make sure your POs are set to Ordered status in Prediko. This ensures they're correctly counted as in-transit.
Import Open POs: Import all open or in-transit POs into Prediko so it accounts for all incoming stock.
WMS Integration: Verify your Warehouse Management System (WMS) integration mapping and ensure the WMS is set as the source-of-truth for stock if applicable.
Transfers & Multi-Location Issues
Experiencing transfer recommendations that seem too low, or transfers not reflecting origin/destination logic correctly?
Min/Max Data: Bulk-import your minimum and maximum stock levels per location. Missing data here can throw off transfer suggestions.
Deactivate Unused Locations: Deactivate any unused locations in Prediko.
Use Transfers Tab: For store transfer recommendations, use the Orders → Transfers tab rather than the Replenish table.
Consolidated View: If you need a consolidated min/max view across locations for easier maintenance, please reach out to our support team.
Bundles / BOM / Raw Materials Friction
If component demand isn't being captured for bundles, or Bills of Material (BOMs) are giving incorrect raw material buy suggestions:
Map Bundles: Ensure bundles are mapped correctly in Shopify (or using a bundles app) so Prediko can accurately sum component demand.
Link
Production Orders First: For production/BOM workflows, create Production Orders first, then trigger "create PO for missing raw materials."
Treat Raw Materials Separately: Consider treating raw materials separately in Prediko (e.g., import initial raw material stock).
Importing / Merging Historical Sales and SKU Merges
Dealing with duplicate SKUs or fragmented sales history leading to split forecasts and wrong recommendations?
Same SKU Mapping: Use Settings → Inventory Settings → Same SKU Mapping to consolidate multiple Shopify product records sharing a SKU.
Historical Data Clean-up: If problematic imported orders are corrupting your historical baseline, removing or adjusting them can help.
Contact Support for Merge: If you have SKU pairs that need their historical data merged in the backend, please contact our support team.
Still seeing an error? We're here to help
If you've worked through the relevant steps and are still seeing an error, don't hesitate to reach out to the support team via chat - Icon at the bottom right of your screen.
It helps us a ton if you can include:
A screenshot of the error message
The SKU name, PO number, or file you were working with
The section of the app where the error appeared
We typically reply within a few minutes and are always happy to get you back on track.