Auctionyx

01 Introduction & features

Thank you for buying Auctionyx! You get a finished, modern auction website that you can rebrand and fill with your own auctions.

Auctionyx is a complete auction website built with Next.js. This full-stack edition includes both parts: the website (auctions, bidding, accounts, admin) and the backend that stores everything in a PostgreSQL database, runs the bidding rules, closes sales on time, sends e-mails and takes card payments.

It runs in two ways:

• Demo mode (no setup): straight after installing, the site runs on built-in demo data from JSON files, with realistic auctions, bidders and bids. Nothing is saved.
• Real mode: give it a PostgreSQL database (one setting, DATABASE_URL) and it becomes your real auction site. Section 9 walks you through it.

Features

02 What's included

After you unzip the download you get the full source code. These are the folders you will use most:

auctionyx-nextjs-template/
├── documentation/          ← this guide (open index.html)
├── docs/                   ← extra guides, including docs/developer/ for developers
├── public/
│   ├── brand/              ← logos and favicons
│   ├── fonts/              ← Sora and Inter font files
│   └── images/             ← hero, category, event and lot photos (+ CREDITS.md)
├── src/
│   ├── app/                ← the pages (one folder per web address)
│   │   └── globals.css     ← colours, fonts, dark mode
│   ├── components/         ← reusable building blocks (header, footer, cards…)
│   ├── backend/            ← the built-in backend (database, bidding, e-mail, payments)
│   ├── engine/             ← the auction rules (proxy bids, closing, invoices)
│   ├── mock-api/
│   │   └── data/           ← ALL demo content, as JSON files
│   ├── api/                ← how the site talks to the API (for developers)
│   ├── services/ actions/  ← data loading and form handling (for developers)
│   └── lib/                ← helpers: money, dates, currency
├── drizzle/                ← database migrations (the table definitions)
├── docker-compose.yml      ← an optional local PostgreSQL for testing
├── .env.example            ← list of settings; copy it to .env.local
├── package.json            ← scripts: dev, build, start…
└── LICENSE.md

The demo data files

All demo content is stored in src/mock-api/data/. These files are used in demo mode only — on your real site, the same content lives in the database and you edit it in the admin area.

03 Requirements

Basic comfort with a terminal (typing a command and pressing Enter) is all you need. Every command is given in full below.

04 Installation

1. Unzip the download and put the auctionyx-nextjs-template folder somewhere easy to find, such as your Documents folder.
2. Install Node.js 20+. Then check that it works:

   node -v

   It should print v20.x or higher.
3. Turn on pnpm (once per computer):

   corepack enable

   If that fails, install pnpm with npm instead: npm install -g pnpm.
4. Open a terminal in the template folder. In VS Code: File → Open Folder, then Terminal → New Terminal.
5. Install the dependencies (takes a minute the first time):

   pnpm install

6. Start the site:

   pnpm dev

7. Open http://localhost:3000 in your browser. You should see the homepage with live demo auctions. To stop the site, go back to the terminal and press Ctrl+C.

When the site is running, the terminal shows something like this (your version numbers and network address will differ):

   ▲ Next.js 15.5.26
   - Local:        http://localhost:3000

 ✓ Starting...
 ✓ Ready in 2.8s

Windows notes

• Install Node.js with the Windows installer (.msi) from nodejs.org. Keep the default options.
• Use PowerShell or the VS Code terminal. Run corepack enable in a terminal opened with Run as administrator if you see a permission error.
• If PowerShell says "running scripts is disabled on this system" when you type pnpm, run this once, then open a new terminal:

  Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

• To copy the settings file: Copy-Item .env.example .env.local (PowerShell) or copy .env.example .env.local (Command Prompt).
• Keep the project in a short path without special characters (for example C:\sites\auctionyx). Very long paths can make installs fail.

macOS notes

• Install Node.js with the macOS installer from nodejs.org, or with Homebrew: brew install node@20.
• Open Terminal, type cd (with a space), drag the template folder into the window and press Enter. This moves you into the folder.
• If corepack enable says "permission denied", run sudo corepack enable and enter your Mac password.
• To copy the settings file: cp .env.example .env.local. Files that start with a dot are hidden in Finder. Press Cmd+Shift+. to show them.

Production build

pnpm dev is for working on the site. It is slower and shows developer messages. To run the optimised version, use:

pnpm build
pnpm start:demo

pnpm start:demo serves the optimised site with the demo data. Once your database is set up (section 9), use pnpm start instead. Plain pnpm start refuses to show the demo data on purpose, so a live site can never go out with the public demo logins (visitors would see a "We'll be right back" page, and the terminal explains why).

Other useful commands in package.json: pnpm lint (code check), pnpm typecheck (TypeScript check), pnpm test (unit tests).

05 Demo accounts

These accounts only exist in the built-in demo data (src/mock-api/data/users.json). Sign in at /login.

The demo data also has eight more bidders (all with password demo1234). Among them are hana.sato@demo.test, who is pending approval, and victor.hale@demo.test, who is suspended. Use them to test the bidder-approval tools.

06 Quick tour of the site

As a visitor (not signed in)

The header has the main menu, a currency switcher (for rough prices only; bids are always in the lot's own currency) and a theme switch (System → Light → Dark). The footer has the site blurb, social links, menu columns, a newsletter form and the legal links. On a first visit, a cookie-consent banner appears.

As a bidder

Sign in as bidder@demo.test, open any live lot and try it:

• Place a bid. The panel shows the lowest bid you can place now. Enter an amount and submit.
• Set a maximum (proxy bid). Open "Set a maximum (proxy bid)" and enter the most you will pay. The system bids for you as others bid (see section 8).
• Watch a lot to follow it on your watchlist and get notifications about it.
• Enquire: ask a question, request a condition report, or leave an absentee or telephone bid.

Your account area at /account:

As an admin

Sign in as admin@demo.test. The admin area at /admin has its own sidebar (a drawer menu on phones). Only admin accounts can open it. Everyone else is sent to their account or to sign-in.

07 Customising

You can change most things by editing plain text files. No coding needed. This section starts with the easiest changes.

Before you edit

• Restart after editing JSON. The demo data is loaded once when the server starts. After you save a file in src/mock-api/data/, stop pnpm dev (Ctrl+C) and start it again.
• Keep the JSON valid. Use double quotes, put commas between items and no comma after the last one. If the site breaks after an edit, paste the file into a JSON validator. VS Code also underlines mistakes in red.
• Money is text. Write prices as strings, like "1500" or "1500.50". Use digits only, with no currency sign and no thousands separator. You can use up to 4 decimals.
• Dates use the ISO format with a time zone, like "2026-10-15T12:00:00.000Z" (the Z means UTC).
• Admin vs. JSON. On your real site you never edit these JSON files: everything below is edited in the admin area (Admin → Settings and Admin → Content) and saved in the database for good. The JSON files only feed demo mode, where admin changes last until the server restarts.

Site name, contact details & social links

File: src/mock-api/data/settings.json (the same fields as Admin → Settings).

Menus & currencies

Real site: Admin → Content → Menus & currencies. Demo data: src/mock-api/data/site.json. Both use the same structure:

"header": [
  { "label": "Home", "href": "/" },
  { "label": "Auctions", "href": "/events" }
]

• navigation.header: the top menu.
• navigation.footer: footer columns. Each has a title and a list of links.
• navigation.legal: the small links at the very bottom. The cookie banner links to the first legal link whose address contains "cookie".
• displayCurrencies, fxBaseCurrency, fxRates: the currency switcher. Rates are how much 1 unit of the base currency is worth in each currency. They are only a guide, so update them from time to time.

Homepage sections

Real site: Admin → Content → Homepage. Demo data: src/mock-api/data/home.json. The homepage shows these sections from top to bottom. Change the text, links and images. The layout stays the same.

Legal & static pages

Real site: Admin → Content lists every page. Click Edit, change the text and save. Write ## at the start of a line for a heading, - for a bullet point, and leave an empty line between paragraphs. New page creates a page such as "About us" at /pages/about-us; add it to a menu so visitors can find it.

Demo data: src/mock-api/data/pages.json. Each page is written as a list of simple "blocks":

{
  "slug": "privacy",
  "title": "Privacy Policy",
  "summary": "One-sentence intro shown under the title and used as the page description.",
  "updatedAt": "2026-08-28T12:00:00.000Z",
  "blocks": [
    { "type": "heading",   "text": "1. What we collect" },
    { "type": "paragraph", "text": "Plain text paragraph." },
    { "type": "list",      "items": ["First point", "Second point"] }
  ]
}

• The three block types are heading, paragraph and list. Text is plain text, not HTML.
• A page is shown at /legal/<slug>. To add a page, add a new entry with a new slug, then add a link to it in site.json under navigation.legal (or footer).
• The entries with slug sell and contact hold the intro text of the /sell and /contact pages.

Auctions (events) & lots

An event is a sale, such as "Classic Motor Car Auction". A lot is one item for sale. A lot either belongs to an event (eventId = the event's id) or stands alone (eventId: null). The demo has 6 events and 46 lots. Six of the lots are standalone.

Event fields: events.json

Lot fields: lots.json

Lot gallery: lot-images.json

{ "id": 1, "lotId": 1, "url": "/images/lots/rolex-front.webp", "alt": "Front of the watch", "sortOrder": 0 }

Add one entry per picture. lotId is the lot's id, and sortOrder sets the order (0 comes first). Always write a short alt text for screen readers.

Dates in the demo (the "time shift")

The demo dates are written as if today were the anchor date in meta.json (27 September 2026). When the server starts, every date is moved forward by the time since that anchor. This keeps live auctions live and "ending soon" lots ending soon, whenever you run the demo. Write your dates relative to the anchor. To use your dates exactly as written, set MOCK_TIME_SHIFT=off in .env.local.

Starting with an empty catalogue

1. Replace the contents of events.json, lots.json and lot-images.json with your own entries.
2. Empty the demo records that point to the old lots: set bids.json, watchlist.json, notifications.json, invoices.json, enquiries.json and audit-log.json to [].
3. On every lot, set currentHighestBid to null, bidCount to 0 and both winner fields to null.
4. Restart pnpm dev.

Colours & fonts

File: src/app/globals.css. All colours are defined as "design tokens" at the top, inside @theme { … }:

@theme {
  --color-brand:   #2563eb;  /* main brand colour (links, buttons, highlights) */
  --color-brand-2: #7c3aed;  /* second brand colour (gradient end)            */
  --color-base:    #ffffff;  /* page background                               */
  --color-surface: #f7f8fa;  /* card / panel background                       */
  --color-ink:     #0e1320;  /* main text                                     */
  --color-success: #16a34a;  --color-warning: #d97706;  --color-danger: #dc2626;
  --font-sans:    'Inter', …;   /* body text  */
  --font-display: 'Sora', …;    /* headings   */
  --radius-md: 14px;            /* corner roundness */
}

1. Change --color-brand and --color-brand-2 to your colours.
2. The gradient is also written out directly in a few places. Search the src folder for #2563eb and #7c3aed and replace them too: in globals.css (the gradient buttons and gradient text), in src/components/home-sections.tsx (the closing banner) and in src/app/global-error.tsx. The soft glow behind the homepage hero uses the same colours written as rgba(37,99,235,…) and rgba(124,58,237,…) in home-sections.tsx.
3. Save. pnpm dev reloads the page automatically.

Changing the fonts

1. Put your font files (.woff2) in public/fonts/.
2. In globals.css, edit the two @font-face blocks at the top: set the font-family name and the src: url('/fonts/your-file.woff2').
3. Update --font-sans (body) and --font-display (headings) to the new names.

The fonts are stored in the template, so no font is loaded from Google or any other server.

Dark mode

Visitors choose System, Light or Dark with the switch in the header. The choice is remembered in their browser. The dark colours are in globals.css, right after @theme. They appear twice, and you must keep both copies the same:

• :root[data-theme='dark'] { … } is used when the visitor picks Dark.
• @media (prefers-color-scheme: dark) { :root:not([data-theme='light']) { … } } is used when the visitor picks System and their device is in dark mode.

Logo & favicon

Folder: public/brand/. The simplest way is to replace these files with your own and keep the same file names:

Browsers keep favicons in their cache for a long time. If you still see the old icon, do a hard refresh (Ctrl+F5 / Cmd+Shift+R) or open a private window.

Images

• Put pictures in public/images/. The demo uses hero.webp, categories/, events/ and lots/.
• A file at public/images/lots/my-lot.webp is written as "/images/lots/my-lot.webp" in the JSON. Start with / and leave out the word public.
• You can also use a full web address (https://…) for pictures stored elsewhere.
• Use JPG or WebP, around 1600 px wide for lot photos, and compress them. Big files make pages slow.
• In the admin panel you can also upload lot images (JPG, PNG, WebP, AVIF or GIF, up to 8 MB each). In demo mode they are kept in memory only. With a real backend, your backend stores them.
• The demo photos come with licences that need attribution (see Credits). If you keep any demo photo on a live site, keep its credit. Replacing them with your own photos is best.

08 How auctions work

The life of an event or lot

Events and lots move through the same six statuses:

In demo mode, time-based changes happen by themselves. A scheduled sale opens when its start time arrives, and a live sale ends at its end time. A lot inside an event can only be live while its event is live.

Placing a bid and the minimum increment

The first bid must be at least the opening price. After that, each bid must be at least current bid + minimum increment. Example: the current bid is $12,500 and the increment is $250, so the next bid must be $12,750 or more. The bidding panel always shows this "next minimum bid".

Proxy (maximum) bidding

Instead of coming back to bid again and again, a bidder can enter a secret maximum. The system then bids for them, raising the price by just enough to stay ahead, up to their maximum. Nobody else sees the maximum.

Reserve price

The reserve is the secret lowest price the seller will accept. Visitors only see "Reserve: not yet met", "met" or "not met". As soon as a bidder's maximum reaches the reserve, the price rises to the reserve. If bidding ends below the reserve, the lot does not sell: there is no winner and no invoice.

Anti-sniping (extra time)

"Sniping" means bidding in the last seconds so nobody can answer. To keep sales fair, a bid placed in the final trigger window pushes the closing time to now + extend. With the demo settings (300 and 120 seconds), a bid in the last 5 minutes means the sale closes 2 minutes after that bid. The close is never made shorter. For a lot inside an event, the whole event's closing time is extended. Change the values in Admin → Settings → Bidding, or set either to 0 to turn anti-sniping off.

Who can bid

• Visitors must sign in first.
• Suspended bidders can never bid. Pending bidders can bid only while "Require bidder approval" is off.
• An admin can set a maximum bid limit for each bidder in Admin → Bidders.
• "Bidding enabled" in Settings switches all bidding off at once.
• To stop abuse, each bidder can place at most 10 bids in 10 seconds.

Buyer's premium, tax and invoices

When a lot ends with a winner (and the reserve is met), one invoice is created for the winner:

The winner gets a "You won" notification and finds the invoice under Account → Invoices. Admins manage invoices under Admin → Invoices: Unpaid → Paid (or Void), and Paid → Refunded. The maths uses whole numbers internally, so there are no rounding errors.

Notifications

Bidders get in-site notifications when they are outbid, when they win, when someone bids on a lot they watch, and when a watched lot is ending soon. Each type can be switched off in Settings. On your real site each notification is also sent by e-mail once e-mail is set up (section 9.2). The demo does not send e-mail.

09 Run your real auction site

The built-in backend is the stock room and till behind the shop window: it stores accounts, auctions and bids in a PostgreSQL database, applies the bidding rules, closes each sale at its end time, picks the winner, creates the invoice and e-mails people. You switch it on with one setting.

1. Set up the database

1. Get a PostgreSQL database. Easiest: create a free project at Neon (neon.tech) or Supabase (supabase.com) and copy the connection string they show you. It looks like postgres://user:password@host/dbname. (Developers can also use docker compose up -d with the included docker-compose.yml.)
2. Put it in your settings file. Copy .env.example to .env.local and set:

   DATABASE_URL=postgres://user:password@host/dbname
   APP_URL=http://localhost:3000

3. Create the tables and starter content (menus, homepage text, legal pages):

   pnpm db:setup

4. Create your admin account:

   pnpm admin:create --email you@example.com --password "a-long-password" --name "Your Name"

   Run the same command again at any time to reset a forgotten admin password.
5. Start the site with pnpm dev, sign in at /login, and open Admin. Fill in Settings (site name, contact e-mail, currency, tax) and Content (your legal pages, homepage and menus), then create your first event and lots.

2. E-mail

Your site sends sign-up confirmations, password-reset links, "you won" / "you were outbid" messages, and tells you (at the contact e-mail in Settings) about new enquiries. Set one of these:

SMTP_URL=smtps://user:password@smtp.your-provider.com:465
# or
RESEND_API_KEY=re_...

MAIL_FROM=Your Auction House <no-reply@your-domain.com>

Any e-mail provider with SMTP works (your host's mail server, Gmail, Brevo, Mailgun, Amazon SES…). Without it, e-mails are only printed in the terminal, which is fine for testing but not for a live site.

3. Card payments (optional)

To let winners pay invoices by card, create a Stripe account and set STRIPE_SECRET_KEY. In Stripe, add a webhook to https://your-domain.com/api/webhooks/stripe for the event checkout.session.completed and put its signing secret in STRIPE_WEBHOOK_SECRET. Invoices then get a Pay now button and are marked paid automatically. Without Stripe, buyers pay you another way (for example bank transfer) and you click Mark paid in Admin → Invoices.

4. Image storage

Photos you upload in the admin are saved in the storage/uploads folder on your server. That is fine on your own server (include the folder in your backups). On Vercel or Netlify the disk is wiped all the time, so there you must use cloud storage such as Cloudflare R2, Amazon S3 or DigitalOcean Spaces: set S3_BUCKET, S3_REGION, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY and S3_PUBLIC_BASE_URL (plus S3_ENDPOINT for R2 or Spaces).

5. Closing sales on time

Sales open and close by themselves while people are browsing. To make sure they also close (and winners get their e-mail) in the middle of the night, set a secret CRON_SECRET (any long random text) and have a scheduler call this address every minute:

curl -fsS -H "Authorization: Bearer YOUR_CRON_SECRET" https://your-domain.com/api/cron/tick

On your own server use crontab; elsewhere a free service such as cron-job.org works. Running it twice by accident is harmless.

6. Go-live checklist

• A production PostgreSQL database in DATABASE_URL (on Vercel/Netlify: the provider's pooled connection string and DATABASE_POOL_SIZE=1).
• APP_URL set to your real https:// address.
• pnpm db:setup and pnpm admin:create run against that database.
• E-mail working (try "Forgot password" with your own address).
• Image storage set up (cloud storage on Vercel/Netlify).
• The every-minute call to /api/cron/tick in place.
• Your own Settings, legal pages, homepage, logo and photos — and no demo data (pnpm db:reset --force removes it). If you keep the starter photos, keep a link to their credits (public/images/CREDITS.md) — their licences require it.
• Decide whether bidders must confirm their e-mail before bidding: Admin → Settings → "Require a confirmed e-mail address" (on by default).
• Admin → Dashboard shows no Before you go live panel — it lists anything above that is still missing.
• Daily database backups (managed databases usually do this for you — check).
• After every template update: pnpm install, pnpm db:migrate, pnpm build, restart.

The full technical guide is docs/developer/BACKEND.md in your download.

7. Using your own backend instead

If you already run another system (Laravel, Django, WordPress…), a developer can connect it instead of the built-in backend. It must answer the documented API; then set API_BASE_URL=https://api.your-domain.com/v1 (it takes priority over DATABASE_URL). See docs/developer/CONNECT-YOUR-BACKEND.md in your download and docs/developer/API-CONTRACT.md in your download.

Set API_MODE=mock to force the demo data (for a public demo copy). A production server needs API_MODE=mock to show demo data at all.

10 Deployment

Whichever host you use, set at least these environment variables: APP_URL (your site's address), DATABASE_URL, the e-mail settings and CRON_SECRET. On Vercel and Netlify also set the S3_… image-storage settings (section 9.4). Run pnpm db:setup and pnpm admin:create once against the production database. For a public demo, instead leave API_BASE_URL empty and set API_MODE=mock plus MOCK_AUTH_SECRET (a long random string).

Vercel (recommended for Next.js)

1. Create a free account at vercel.com.
2. Put the project in a private Git repository (GitHub, GitLab or Bitbucket). Don't upload node_modules, .next or .env.local. The included .gitignore already leaves them out.
3. In Vercel click Add New → Project and import the repository. Vercel detects Next.js and pnpm by itself. Keep the default build settings.
4. Open Environment Variables and add APP_URL, DATABASE_URL (the pooled connection string), DATABASE_POOL_SIZE=1, the e-mail, CRON_SECRET and S3_… settings, and any others you need.
5. Click Deploy. After a minute or two you get an address like your-project.vercel.app.
6. Add your own domain under Settings → Domains, then update APP_URL to it and redeploy.

Netlify

1. Push the project to a private Git repository (as above).
2. In Netlify choose Add new site → Import an existing project and pick the repository. Netlify detects Next.js by itself.
3. Build command: pnpm build. Leave the publish directory as Netlify suggests.
4. Under Site configuration → Environment variables add APP_URL, DATABASE_URL, the e-mail, CRON_SECRET and S3_… settings, and any others. Set NODE_VERSION to 20 (or newer) if the build uses an older Node.
5. Deploy, then connect your domain.

Your own server (VPS)

Any Linux server with Node.js 20+ works.

1. Upload the project (or git clone it), then in the project folder run:

   corepack enable
   pnpm install --frozen-lockfile
   cp .env.example .env.local   # then edit .env.local
   pnpm build

2. Start it and keep it running with a process manager such as PM2:

   npm install -g pm2
   pm2 start "pnpm start" --name auctionyx
   pm2 save

   The site now listens on port 3000. Use pnpm start -p 8080 for another port.
3. Put a web server such as Nginx or Caddy in front of it, and serve the site over HTTPS. In production the sign-in cookie is marked "secure", so sign-in only works over https://.
4. Install PostgreSQL on the server (or use a managed one), set DATABASE_URL, run pnpm db:setup and pnpm admin:create, and add the every-minute crontab line from section 9.5.
5. After every update: pull the new files, then run pnpm install, pnpm db:migrate, pnpm build and pm2 restart auctionyx.

Shared hosting that only runs PHP cannot run Next.js. You need a host that runs Node.js.

11 Environment variables

Put these in .env.local for your computer, or in your host's environment settings. For the demo none are needed; for your real site you need at least DATABASE_URL, APP_URL, the e-mail settings and CRON_SECRET. Restart or redeploy after changing them. The complete list with explanations is in .env.example.

12 FAQ & troubleshooting

13 Support

We are happy to help you get Auctionyx running.

How to contact us

1. Check this guide and the FAQ first. Many answers are already here.
2. E-mail waafaaofficial@gmail.com.
3. Include your order number or the e-mail address you used at checkout, your Node.js version (node -v), your operating system, what you did, what you expected, and the full error message or a screenshot.

Response time: within 1–2 business days, Monday to Friday, Bangladesh time (GMT+6).

Support period and refunds: these follow the terms on the Auctionyx product page at waafaa.com, where you bought the template.

Seller: WaaFaa. Available at waafaa.com.

14 Credits

Fonts

Both fonts are free to use, including commercially, and are included in the template.

Images

The demo event and lot photos come from Wikimedia Commons under redistributable licences (Public Domain, CC0, CC BY and CC BY-SA). The full list with authors, licences and source links is in public/images/CREDITS.md. They are for the demo only and are not part of what you are licensed to resell. If you keep any CC BY or CC BY-SA image on your site, keep its credit.

Software

Built with Next.js, React, Tailwind CSS, TypeScript and Zod. All are open-source under the MIT licence (TypeScript: Apache 2.0).

15 Changelog

Full-stack edition (29 September 2026)

• Built-in backend on PostgreSQL: accounts with secure sessions, e-mail verification and password reset, two-factor sign-in, and limits against password guessing and spam.
• Real bidding: each bid is processed safely one at a time per lot, a double-click never places two bids, proxy bids, reserve, anti-sniping.
• Sales open and close on time (automatically and with an every-minute cron), reserve-aware winners, one invoice per won lot.
• E-mail (SMTP or Resend), Stripe card payments with automatic refunds of duplicate payments, image uploads to disk or S3-compatible storage.
• New Admin → Content: edit legal pages, create new pages, and edit the homepage and menus without touching files. Newsletter subscribers export.
• Setup commands: pnpm db:setup, pnpm admin:create, pnpm db:demo, pnpm db:reset --force, pnpm db:migrate.

Version 1.0.0 (27 September 2026)

• Initial release.
• Public site: home, auctions, auction pages, catalogue with search, filters, sort and pagination, lot pages with live bidding, sell, contact and legal pages.
• Bidding: minimum increment, proxy (maximum) bids, hidden reserve, anti-sniping, bid history, watchlist and lot enquiries.
• Accounts: register, sign in, e-mail verification, password reset, two-factor authentication, dashboard, bids, watchlist, notifications and invoices.
• Admin: dashboard, events, lots and galleries, bidders, users, invoices, enquiries, consignments, audit log, reports with CSV export, and settings.
• Built-in mock API with demo data and automatic date shifting. Connect your own backend with one setting.
• Light, dark and system themes, and a display-currency switcher.