AuctionWorx Enterprise

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

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.

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 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.

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.

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.

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.