StorIQ help center

Hit "Start free trial", name, email, company, and a password (8+ characters, with a number and a symbol). You will be in the dashboard in under a minute, trial running, no card asked.

Dashboard → Facilities → Add facility (name, address, website). Team members are invited from the Team page. Plan caps apply, Starter: 1 facility / 3 users; Growth: 5 / 10; Scale: 15 / 25, with overages available.

Use the "Forgot password" link on the login page. You will get a single-use reset link by email that expires in one hour.

Account email and company details can be updated under Dashboard → Settings. The account owner manages billing and team access.

Contact us and we will delete your account and all associated data. You can export everything first from the dashboard.

Yes, message us from the contact page and we will walk through your first data import, whether it is a CRM pull, an API push, or a CSV.

The trial already gives you the full Scale plan, so there is nothing to upgrade to mid-trial. When the trial ends, pick whichever plan fits from the billing page; your data and settings carry over.

When the subscription ends, team members lose dashboard access along with the account. Your data is retained and exportable, and everyone regains access if you resubscribe.

Your data is kept. If the new plan allows fewer facilities or seats, you choose which facilities stay active; the rest become read-only until you upgrade again or add overage slots.

Dashboard → Facilities → Add facility. Enter the name, address, and website. Then either connect your CRM, push data via the API, or upload a CSV, recommendations appear once we have rates and occupancy.

Facilities → pick a facility → Upload. Columns: size, tier, street_rate, occupancy_pct, move_ins_mtd (a template is downloadable on the upload page). For competitor rates use: competitor_name, size, rate, promo, observed_at, source_url.

Create an API key under Dashboard → API keys (shown once, store it safely). Push data to POST /api/v1/sync with your facility identifier and a dated payload. It is an idempotent upsert keyed on facility + date, so re-sending a date replaces the earlier payload instead of duplicating it.

Open a facility and click Recommendations → Generate. We apply the fourteen pricing rules to every unit size and show the reasoning. Regenerate after each new upload or sync. Every run is saved with its inputs, and the "what changed and why" log compares runs.

Upload them by CSV (competitor_name, size, rate, promo, observed_at, source_url) or push via the API. Your manual entries are never overwritten by automatic tracking. You can also suggest a missing competitor from the facility page.

Include active promos in your sync payload (name + depth_pct). The engine applies the promo-depth rule: deep promos are for acquiring first-time move-ins, never for the in-place base.

Facilities, rates, and recommendations can be exported from the dashboard anytime. Your data is yours.

Check your columns match the template exactly: size, tier, street_rate, occupancy_pct, move_ins_mtd, total_units. Download a fresh template from the upload page (Facilities → pick a facility → Upload) and compare it against your file's header row.

Exactly these headers: size, tier, street_rate, occupancy_pct, move_ins_mtd, total_units. Example row: 10x10,Regular,189,94,6,10. Extra columns are ignored, but missing or misspelled headers will fail the upload.

Use these headers: competitor_name, size, rate, promo, observed_at, source_url. Example: Acme Storage,5x5,95,,2026-09-30,https://acmestorage.com/rates. Leave promo empty when there is none.

Rows that fail validation are quarantined instead of imported, so bad data never poisons your recommendations. Check the quarantine count on Dashboard → Data sources, fix the flagged rows (usually a bad rate, an unknown size label, or a missing field), and re-upload.

CSV or .xlsx both work. Save as UTF-8 to avoid garbled characters, keep headers in the first row, and put data on the first worksheet if you use Excel. For very large files, split them by facility and upload one at a time.

Double-check your email spelling and password, then use the "Forgot password" link on the login page for a reset link (single-use, expires in one hour). If you signed up recently but never verified, logging in will resume the verification step instead.

Check your spam folder first, then go back to the /verify page and request a fresh code with the resend option. Codes expire, so use the newest one. If nothing arrives after a few tries, contact us from the contact page.

A blank dashboard almost always means no data has arrived yet. Connect your Stora account, push via the API, or upload a CSV from Facilities → Upload, then regenerate recommendations. New accounts show labeled sample data until your first real sync lands.

The engine will not guess when evidence is thin, usually because competitor rates are missing for that size. Add the missing input: upload competitor rates by CSV, trigger a manual competitor refresh, or connect Stora so occupancy and rates flow in automatically. The recommendation appears as soon as the data supports it.

A 403 means Stora rejected our access token, usually because permissions changed on the Stora side. Reconnect from Dashboard → Data sources: disconnect the Stora account and connect it again, approving all requested permissions. Your existing data is untouched.

Check Dashboard → Data sources for the last successful sync time and any error notes. Syncs run every 24 hours by default; if the last sync is old or shows errors, try a manual pull from the same page, and reconnect the account if it keeps failing.

The push needs the write permission, which Stora grants separately from read access. If your account was connected before that permission existed, reconnect from Dashboard → Data sources and approve the updated permissions, then retry the push.

Your API key is missing, wrong, or revoked. Send it as an Authorization: Bearer header. Keys are shown only once at creation, so if you lost it, revoke the old one and create a new key under Dashboard → API keys.

The payload shape is wrong. Check that your JSON includes the facility identifier and a dated payload matching the documented schema. Pushes are idempotent upserts keyed on facility plus date, so re-sending a corrected payload for the same date safely overwrites the bad one.

No. Every push is an idempotent upsert keyed on facility plus date, so re-sending the same date updates the existing record instead of duplicating it. Re-send freely if you need to correct data.

Automatic discovery finds most nearby competitors, but not all. Suggest the missing one from the Competitor tracker tab with their name and website, and they will be researched on the next refresh.

Use "Override a rate" on the Competitor tracker tab: pick the competitor, enter the size and the correct monthly rate, and save. Your override is marked as yours, feeds your recommendations, and automatic refreshes will never overwrite it.

You get 8 manual refreshes per facility per rolling 24 hours. Wait for the window to reset, or rely on the automatic weekly refreshes that run in the background. The remaining count is shown on the Competitor tracker tab.

Update your card on the billing page; Stripe retries automatically and we email you about it. Your access continues during the retry window. If payment ultimately fails, the subscription pauses until billing is updated, but your data is never deleted over a failed payment.

Stripe emails you a payment receipt from receipts@storiq.io after every charge. The billing page shows your plan, status, and billing cycle but does not list past invoices; your emailed receipts are the record.

Plan changes apply when Stripe confirms payment via webhook, usually within a minute or two. Refresh the billing page; if it still shows the old plan after a few minutes, contact us from the contact page with your account email and we will sort it out.

Check your spam folder and make sure storiq.io senders are not blocked. Verification codes come from the signup flow (resend from /verify), the weekly digest only sends if enabled under Dashboard → Digest, and rate-change reminders only fire for scheduled changes you created.

Try a hard refresh (Ctrl+Shift+R or Cmd+Shift+R) and check your connection. If a specific facility page hangs, it is usually still crunching a large recommendation run; wait a minute and reload. Persistent slowness across pages is worth reporting via the contact page.

Message us from the contact page on storiq.io. Include your account email and, if it is a data issue, the facility name so we can look straight at the right records.

Scheduled changes never apply themselves; when one comes due we email you a reminder and you apply it with one click from the Rate changes page, which then feeds into Push rates. Check the Rate changes list to confirm the entry is still there and the date has not passed unnoticed.