Skip to main content

Settings

In this article, you will learn how super admins manage operating settings that affect shopping, cart reservations, sign-in timeout, and upload column recognition.

Screenshot placeholder

Add screenshots of Settings tabs, availability settings, cart reservation settings, sign-in timeout, and upload column configuration.

Before You Start​

Coordinate setting changes with the operations team. Availability, cart, sign-in, and upload column changes can affect how users work immediately.

Manage Availability And Cart Settings​

  1. Open Settings.
  2. Choose General.
  3. Review the minimum days before arrival.
  4. Review the cart reservation time.
  5. Update values when the operations team agrees on a change.
  6. Save changes.
  7. Tell customer-facing teams when the change affects shopping behavior.

Availability settings control when products can appear to customers. Cart settings control how long items are held while a customer reviews the cart.

What Happens When You Save​

Saving applies every change on the page together. If any part of the save cannot be completed, nothing is changed and the page reports the failure — your previous settings stay in place until a save succeeds.

This matters most for the arrival-day settings, which work as a pair: the days you treat as regular arrivals, and whether customers may order for other days. Those two decide which products customers can buy and which orders carry an off-day charge, so they always take effect together. You will never end up with one applied and the other not.

Turning off "allow other days" takes effect immediately, including for customers who already have such products in their cart. Those customers can no longer add more of them or increase the quantity, and cannot place the order. They can still reduce the quantity or remove the line, and the cart offers to remove it for them at checkout. Stock held by those lines is released as soon as they are removed, or when the cart reservation time runs out.

If a save fails, check the values you entered and try again. A value the system cannot accept — for example an arrival-day selection that did not save correctly — is reported without changing anything.

If Someone Else Changed These Settings First​

Two administrators can have this page open at the same time. If any of these settings changed while your page was open, your save is refused rather than applied: the page tells you what happened, nothing is written, and the values shown are reloaded so you can see what is now in effect.

This is deliberate. Because your page only sends what you edited, a save made against an out-of-date view could otherwise combine your change with someone else's and produce a configuration neither of you chose — for example your "allow other days" setting applied on top of their new regular arrival days. Refusing the save keeps that from happening.

When you see this, review the reloaded values, make your change again if it is still the one you want, and save.

Manage Sign-In Timeout​

  1. Open Settings.
  2. Choose Security.
  3. Review the sign-in timeout.
  4. Choose the timeout your team wants.
  5. Save changes.
  6. Let users know if the timeout becomes shorter.

Shorter timeouts can improve account safety but may interrupt users more often.

Manage Simultaneous Sessions​

  1. Open Settings.
  2. Choose Security.
  3. Review Allow simultaneous sessions.
  4. Choose the setting your team wants.
  5. Save changes.

When simultaneous sessions are allowed, one person can stay signed in on several devices at once — for example a laptop and a phone.

When they are not allowed, each person can be signed in on one device at a time. Signing in somewhere new ends the earlier session, and that device returns to the sign-in page the next time it is used. Tell your team before you turn this off, so nobody is surprised to be signed out.

Manage Upload Column Configuration​

  1. Open Settings.
  2. Choose Column Configuration.
  3. Add a column when farm files include a field Floral Stock should recognize.
  4. Add aliases for common header names.
  5. Remove a column only when it should no longer be used for new uploads.
  6. Save configuration.
  7. Ask farms or administrators to test the next upload when column changes are important.

Column aliases help uploads match farm spreadsheets even when each farm uses slightly different header names.