AuctionWorx Enterprise
built cleaner, friendlier, and extensible.
AuctionWorx Enterprise is a complete auction website solution.
It can be configured and ready to deploy as-is or customized and modified to suit your business needs.
AuctionWorx Enterprise includes Auctions, Fixed Price, and Classified listings. All listing formats can be turned on/off and configured through the Admin Control Panel.
Enable multiple vendors to sell on your marketplace - allow sellers to post listings and optionally charge fees
Single Seller Mode - list your own products as the only seller, replace or build on to existing sales channels, or liquidate assets
Offer buyer checkout with sales invoicing, sales tax, shipping options, and multiple payment options.
AuctionWorx Enterprise intelligently suggests the grouping of items purchased from each seller, according to shipping and payment options, for each invoice.

Examples:
- A Real Estate listing may contain custom fields for : Square feet, Number of Bedrooms or Year Built.
- A Vehicle listing may contain custom fields for : VIN number or Mileage.
- A Fashion listing may contain custom fields for : Size or Condition.
AuctionWorx Enterprise › Features
Whats New in v1.1?
Feature List
- Enable multiple sellers to post
- Charge listing Fees
- Single Seller mode
- List your own products
- Enterprise Architecture
- ASP.NET MVC 2
- jQuery JavaScript Library
- ASP.NET 4.0 (C#)
- Windows Communication Foundation (WCF)
- Microsoft SQL Server 2008 (or Express)
- Registration
- Feedback
- Custom User Fields
- My Account Buyer/Seller Controls
- Internal Messaging System
- New Message Indicator
- Sales Invoicing with checkout options
- Credit Card Payments
- PayPal Payments
- Flat rate shipping options
- Sales Tax
- Categories
- Regions
- Advanced search
- Accounting Service
- Common Service
- Listing Service
- Notification Service
- Scheduler Service
- Site Service
- User Service
- Templates based on master pages
- CSS based design
- Extend using Provider model
- Developer API
- N-tier application architecture
- SSL support
- Encryption (3DES)
- Microsoft AntiXSS
- External authentication through Membership Provider
- Forgot Password Reset
- Support for load-balanced environments
- Microsoft Azure support
- Database level paging
- Caching
- Web-based Site Administration
- CMS - Site Content HTML Editor
- CMS - Social media content
- CMS - Footer and Header Scripts
- Category Administration
- Banner Ad system
- Email notifications with templates
- Standard Auctions
- Fixed Price Sales
- Classified Ads
- Allow listing formats by category
- Proxy Bidding
- Reserve Price
- Buy Now
- Auto-extend (Sniper Protection)
- Configurable Bid Increments
- Multiple Image Uploads (Asynchronous)
- Custom Listing Fields
- YouTube Video Support
- Relist
- Featured and Decoration Options
- Add to Watch List
- Price Field Updates via AJAX (Asynchronous)
- Specify End Date/Time (Optional)
- Multiple Language support
- Multiple Currency support
- Server Time Zone Offset
- Clean, semantic HTML
- Friendly URLs
- Sitemap
AuctionWorx Enterprise › Developers
An Enterprise-Class .NET solution built from the ground up and based on over 9 years of experience and customer feedback. We started by developing a solid base framework - FrameWorx is an extensible platform for ecommerce marketplaces with its first incarnation as AuctionWorx.
Technologies
- ASP.NET 4.0
- Microsoft MVC 2
- Microsoft WCF
- Microsoft Azure
- jQuery & jQuery UI
- AJAX & JSON
- SQL Server 2008
Architecture
We selected Microsoft’s Model-View-Controller (MVC) technology as the forward facing web technology. It greatly enhances development efforts by segregating domain logic from presentation logic and from basic presentation HTML.
- Complete control over HTML Markup
- Rich AJAX and jQuery integration
- SEO-friendly URLs
- Test Driven Development (TDD)
The Business Logic Layer (BLL) contains the business logic of FrameWorx; the foundation of AuctionWorx. This layer is designed to execute in-process with the presentation layer or as separate Windows services accessible via Windows Communication Foundation.
The Data Access Layer (DAL) handles all Create/Read/Update/Delete operations for AuctionWorx. It was written with the provider paradigm so that the underlying backing store could be rewritten if necessary. We chose to implement Mindscape’s LightSpeed O/RM.
Business Logic Components
The Accounting Service handles all invoicing and payment transactions of site fees and third-party sales. Site fees are any fees that are triggered by the event system, typically when a seller utilizes features of the site such as listing items. Third-party sales are the buy/sell agreement between a seller and the eventual winner of a listing (highest bidder of an auction, purchaser(s) of a fixed price listing, etc).
The Accounting Service supports a Fee provider model which allows developers to assess fees based on events and listing state.
The Account Service supports a Payment provider model which allows payments to be made either synchronously, as in the case of Authorize.Net; or asynchronously, as in the case of PayPal. The provider model allows additional payment providers to be implemented and integrated into the platform.
The Common Service handles many of the commonly used components of AuctionWorx such as the Custom Field system, and the hierarchical Category system.
The Listing Service handles the workflow of creating, editing, and resolving listings in addition to buyer initiated events (bids).
The Listing Service supports a Listing Type provider model which allows additional listing types to be defined. The software includes Standard Auctions and Fixed Price listings.
The Site Service supports the presentation layer and administrative interface.
The Notification Service handles all outgoing emails from the site asynchronously so as not to impact performance.
The Scheduler Service triggers listing starts and resolutions.
The User Service provides user and account services and is extended by the ASP.NET membership provider to provide login functionality.
Multiple Deployment Options
In this mode, the BLL and the DAL execute within the IIS worker process context which includes the Scheduler and Notifier, in addition to the front-end MVC. MVC communicates with the BLL via client classes with In-Process access to the BLL Services. The BLL communicates with the DAL In-Process. This is most useful in environments where the installation needs to be kept simple, or where multiple AuctionWorx sites could be executing on the same IIS webserver.
Both the BLL and DAL execute within a Windows Service which includes the Scheduler. There is an additional Windows Service for Notifications since there is such a clear demarcation between other BLL services, and Notification fulfillment. Additionally, Notification can be setup to be run on a more appropriate server, perhaps closer to, or even on, an outgoing mail server if the customer so chooses. MVC still executes within the IIS worker process context. MVC communicates with the BLL via client classes with Windows Communication Foundation (WCF) service remoting to the BLL/DAL Windows Service. This mode is most useful in environments which require scalability. An example of this would be a web farm of more than one web server serving the MVC layer, an application server serving the Windows Services for BLL/DAL, and optionally a notification server serving Notification fulfillment.
Development
The source to the MVC project, views, and controller code is included. This will allow a developer to change any aspect of the presentation layer. The remaining functionality can be extended by implementing providers and making calls to the API. The BLL and DAL are available only as compiled runtime binaries however the source to these are not necessary to implement any required changes.
The MVC project source is included: controller code (presentation logic), web pages (ASPX), web partials (ASCX), and any related HTML resources can be modified. All MVC related source code is commented and documented.
View code exists to actually present the data (model) to the user. There usually isn’t much logic in View code, except logic pertaining to presentation, such as looping through collections, etc.
Controller code exists to prepare the data (model) for presentation by the View. Therefore, calls to the client are usually made in the Controller code. Changes that involve modification to the data about to be displayed or the form data entered can be made here.
These static HTML assets are used by Views and can be modified as desired.
BLL: Providers
The provider model design pattern allows specific functional areas to be implemented and integrated into the platform using a dependency injection container (Microsoft Unity). As such, developers can implement additional or replacement providers to the following functional areas:
The Listing Format Provider allows you to define your own listing formats. Standard Auction and Fixed Price are both included with the software.
For example, if you wanted to implement a Dutch or a Reverse Auction, you would implement your own Listing Format Provider that contains the necessary business logic.
The Membership Provider allows you to implement your own authentication mechanism.
For example, you may have an existing site with existing users and rather than setup each of your existing users in AuctionWorx, you could implement a Membership Provider that authenticates users against your existing user data.
The Fee Provider allows you to assess fees, based on events and the listing state. The Fee Provider is queried any time a listing is created, updated, closed, etc… to calculate site fees.
For example, you may want to implement your own Fee provider if you have special cases where certain users should receive discounts or an existing database is queried.
The Payment Provider allows you to implement payment methods to be made either synchronously, as in the case of Authorize.Net; or asynchronously, as in the case of PayPal.
For example, you may want to implement Google Checkout and offer that as a payment option to your users.
The Media Asset Provider allows you to define new types of media that can be included in Listings and Listing Actions (Bids, Purchases, etc…). The system provides interfaces for generating, storing, and referencing media.
For example, you may want to implement saving and storing listing images with a specific image hosting service, or you may want your sellers to be able to embed YouTube videos with their listings.
The Encryption Filter allows you to implement other encryption methods into the system to encrypt/decrypt passwords and credit card numbers. Currently, a TripleDES symmetric encryption filter is included with the software.
For example, you may want to implement AES symmetric encryption, or change the default encryption keys.
AuctionWorx Enterprise › Online Demo
Our online demo is a great way to explore what our software can do.
The demo also provides access to the Admin Control Panel so you can actually try out configuration options.
Note: the online demo resets periodically throughout the day in order to maintain a consistent experience.
A few minor functions and settings are also disabled for security reasons.
AuctionWorx Enterprise › System Requirements
- Windows Server 2008
- IIS 7.0/7.5
- .NET Framework 4.0
- MS SQL Server 2008
- Copyright © 2002-2012. RainWorx Software. All rights reserved.
- Privacy All personal consumer information submitted through this web site will be held confidential within the company.

Highlights
Features
Developers
Online Demo
Requirements

