Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for bidder-collects sales process. #26

Open
chmarr opened this issue Oct 16, 2013 · 0 comments
Open

Support for bidder-collects sales process. #26

chmarr opened this issue Oct 16, 2013 · 0 comments

Comments

@chmarr
Copy link
Owner

chmarr commented Oct 16, 2013

Support for Anthrocon's sale's process.

Constraints:

  • bidder IDs hand-written onto bid sheets. (future might add printed stickers, or barcode stickers)
  • no "after close" data collection. All "bid data" is collected during the sales process
  • pieces (with bids, and those sold with 'after show' option) are collected by bidders and brought to sales desk.
  • bidder IDs are non-numeric. (Already supported)
  • artist IDs are non-numeric. (Covered in other issue - I think)

Ideas:

  • Barcodes on bid-sheets can still be of use, but there's still significant hand data-entry for each piece that might make barcodes more trouble than its worth
  • At sales time, bidder ID is entered, ID confirmed, then per sheet: Piece ID entered, bidder ID confirmed (if not a 'after show'), price entered, type of bid (standard, after-sale, voice auction) entered. Then normal cashier process.
  • Possibly add support for recording number of bids, for analytics purposes.
  • Add support for quick "no sale" reporting of a stack of bid sheets, either during artist check-out, or post show.
  • Add support for quick "uncollected" data entry, either before or after pieces are grouped by bidder.

This is similar to the standard "support after show sales" idea, except that we'll want to enter the bid type at sales time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant