SaleCart

10Keeping your store up to date

Good habits for a busy store, and how SaleCart itself is kept up to date.

A simple routine #

Every day

  • Check the dashboard: To fulfil, Awaiting EFT and Reviews to check.
  • Confirm EFT payments that came in, and ship paid orders.

Every week

  • Look at Low stock on the dashboard or under Inventory, and reorder.
  • Publish or reply to new reviews.
  • Glance at Reports to see what's selling.

Every month or season

  • Update your home page banners and specials in the page builder.
  • Refresh your price list and send it to your regular customers.
  • Remove or archive products you no longer sell (set their status to Archived: past orders keep their details).

Updating products quickly #

  • One product: open it under Catalogue → Products, change what you need and press Save.
  • Prices for many products: tick them on the product list and use the bulk price change, or put them on special with Marketing → Sales & specials.
  • Stock for many products: Catalogue → Inventory, or export, edit and import a CSV.
  • New season: set new products to Draft while you prepare them, then switch them to Active together.

SaleCart updates #

SaleCart (formerly EmCart, and before that DemoCart) keeps improving. Your licence includes every new version released for a period after you bought SaleCart (the Downloads section of your afriweb.co.za account shows until when), and you install them yourself in Settings → Updates (below), with no FTP. When a new version your licence includes is out, a notice at the top right of the admin says so (the owner sees it). With a Support Plan, your SaleCart support team installs them for you.

  • The version you're on is shown at the bottom of every admin page (for example SaleCart version 1.0.19).
  • Updates never touch your products, orders, customers, pictures or settings.
  • When an update changes the database, the change is applied automatically the first time the store is opened after the update.
  • Your nightly backups mean there is always a recent copy to fall back on. Before a big update you can press Back up now on the Backups page.

The Features page on your store's demo site lists everything SaleCart can do, including the newest additions.

Installing an update #

Settings → Updates (the owner only)

First, once: enter your licence number under Your licence on the same page and press Save and check. It is in the Downloads section of your afriweb.co.za account (it looks like SC-ABCD-EFGH-JKLM). The store checks it with afriweb.co.za once a day and shows until when your updates are included, and when a new version is available.

When a new version is available, the notice at the top right of the admin says SaleCart 1.28.0 is available (with the new version's number): press Update.

  1. Press Download and check under Your licence. The store downloads the new version from afriweb.co.za itself. You can also download the update file from the Downloads section of your afriweb.co.za account (the smaller file ending in `-update.zip`) and choose it under Install an update instead.
  2. Nothing changes on your store yet: SaleCart checks that the file is genuine (signed by SaleCart), that it is for your edition and newer than your store, and that your hosting has room and lets the files be written. It also checks that your licence includes this version: one released after your licence's updates ended can't be installed (you keep every version released before then).
  3. Read what it will do: how many files are replaced, added and removed, whether the database changes, what happens to your own changes (below), and what's new.
  4. Press Install now, or Install tonight at 02:00 to have it done while the store is quiet (it starts at 02:00, or the next time the store is visited after that).

When your updates have ended

A version released after your licence's updates ended isn't included: the notice then says SaleCart 1.28.0 is out. Your updates ended on … and Extend licence takes you to Your licence. To extend your licence, contact Afriweb and quote your licence number. Once Afriweb has extended it, press Check again under Your licence (or wait for the store's daily check): the notice changes to Update.

While it installs, shoppers see Back in a moment for a few seconds and their carts are kept. A database backup and a copy of every file that changes are made first. Afterwards the store's home page, sign-in page and a product page are checked: if any of them doesn't answer properly, everything is put back at once and you get an email saying why. When it works, you get an email too.

Your own changes

  • Custom CSS & code, themes, pages, emails and settings are kept: they live in your database, not in SaleCart's files.
  • Approved custom files (shown as Approved custom on the Code check) stay as they are when the new version doesn't change that file. When it does, the update waits before it starts and lists the files, so your custom work is never undone by accident: it needs merged copies of those files from Afriweb (your custom work combined with the new version's changes). The store tells Afriweb which files need merging, asks afriweb.co.za for the merged copies once a day and checks the update again when they come; meanwhile the notice says Afriweb is preparing your custom files. The merged copies are installed in place of SaleCart's, and they stay Approved custom.
  • Other changes to SaleCart's files stay as they are when the new version doesn't change that file. When it does, the update lists them and replaces them only when you tick These files may be replaced with SaleCart's (a copy is kept with the update). To keep such a change through updates, ask Afriweb to approve it first. Changes nobody approved must also be accepted on the Code check first.
  • Add-ons: files on your store that aren't SaleCart's (another developer's add-on, for example) are left alone, and the plan says how many there are. If the new version adds a file in the same place, it is listed with the files above and replaced only when you tick the box.

Undo

For 14 days, Undo this update under Updates on this store puts the old version back:

  • If the update didn't change the database, it puts back the old files and keeps every order, customer and change made since.
  • If it did change the database, it also restores the database as it was just before the update, but only while no order or customer has arrived since. Otherwise undo isn't offered, because it would lose them: the fix then comes as the next update.

The button tells you which it will be before you confirm.

Code check #

Settings → Code check shows whether your store's code is still exactly what Afriweb shipped. Each SaleCart version comes with a list of all its code files and a fingerprint of each, signed by Afriweb. The store checks that the list really is Afriweb's, then compares every code file with it. It checks by itself once a day; the owner can press Check again now.

  • Unchanged ✓: nothing was changed. Updates can go ahead as usual.
  • Changed: the page lists each file that was changed, added or is missing, with its size and date. This happens when someone (you, a developer or an AI tool) edits SaleCart's files on the server.
  • Approved custom (Afriweb): changes Afriweb made for your store and signed. They are not counted as changes.
  • Can't be verified: the fingerprint list itself isn't Afriweb's. This counts as changed.

Pictures, fonts, your settings file, uploads, logs and backups aren't code, so they are never checked.

Why it matters: an update replaces SaleCart's files with the new version, so changes made outside Afriweb can be overwritten, or can stop working. When the check finds changes Afriweb didn't approve, the owner sees Before the next update: tick the box and press I understand: record my acceptance to confirm you understand the risk. Your name, the time, your internet address, the version and a fingerprint of the list are recorded. Afriweb's update tools won't update a store with changes nobody accepted. If the changes are different later, you'll be asked again.

Send the result to Afriweb (optional, off unless you switch it on): with a Support Plan, the store can send the result once a day, so Afriweb knows before an update. It sends only the version, the result, the counts and the changed files' names and fingerprints, never their contents or any customer information. Paste the Report key from Afriweb (it starts with `ecr1.`) in the same box and press Save: nothing is sent without it.

Your licence agreement #

SaleCart is licensed to you under the SaleCart Software Licence Agreement, which was accepted when your store was installed. Settings → Licence (or Licence at the bottom of any admin page) shows who accepted it, for which business and when, along with the full agreement. Press Download a copy to keep one on file.

In short: the licence lets you run one store, and support and version updates are an optional monthly Support Plan. Read the Important terms box at the top of the agreement for the main points.

When the agreement gets a new version, the owner is shown it once at their next visit to the admin and can accept it or press Not now. Version 1.4 adds the terms about changes to the code (clauses 21 and 22).

Getting support #

If something isn't working as expected:

  1. Search this manual: the answer is often here.
  2. Note what you were doing, the page address and any message on screen.
  3. Contact your SaleCart support team with those details.
Buy nowR1999