Skip to content
Ailaaj Academy

Faster images & smoother busy hours — Ailaaj One 1.4.8

Faster images & smoother busy hours

Release date: 16 July 2026
Version: Ailaaj One 1.4.8
Status: Live in production
Who it helps: Shoppers on the online store, staff uploading product photos, warehouse teams attaching invoices, and everyone signing in during busy periods

In short

We made two behind-the-scenes upgrades that people will notice as:

  1. Faster product photos and files
  2. Fewer problems when many people use Ailaaj at once

Day-to-day screens and buttons stay the same — this is about speed and reliability.

Improvements

Faster photos and files

  • Product pictures on the website and in product setup load more quickly.
  • Uploaded documents (such as supplier invoices on goods receiving) open more reliably.
  • Photos and files no longer depend as heavily on the main Ailaaj server, so image traffic does not slow down the rest of the system as much.

Smoother busy hours

  • When many staff members and customers are active at the same time, the system is better at sharing capacity.
  • Sign-in and everyday work are less likely to fail just because the system is busy.
  • We did this on the same production server — no larger machine required for this step.

Product setup (PIMS)

  • New product photos are saved with clear names based on the product, which helps the website and keeps the catalog tidy.
  • Existing Ailaaj product photos were moved onto the new faster image network.

Online store

  • Shoppers should see product photos load faster.

Goods receiving

  • Invoice and attachment uploads use the new file network.

Fixes

  • Goods receiving: Attaching a supplier invoice no longer fails with a confusing “network / blocked” style error in cases caused by a bad storage setting.
  • Online store: Product pages no longer fail to load when a system connection setting was accidentally left empty.

Benefits for the business

  1. Shoppers get a snappier catalog — photos arrive faster.
  2. Staff keep working at peak times — less chance of being locked out when the store is busy.
  3. Website and staff tools interfere less with each other — heavy internal use is less likely to hurt the online store, and vice versa.
  4. Lower risk of sudden “everything stuck” moments during spikes.
  5. Invoices and attachments are stored more reliably for warehouse and accounts workflows.

Notes for support / IT

  • Older on-server file storage is stopped; data is kept on disk if a rollback is ever needed.
  • App APIs use the database connection pooler; sign-in services stay on the direct database path.
  • After changing browser-facing storage settings, a production redeploy is required.
  • Technical runbook (internal): docs/internal/postgres-connection-capacity-plan.md