General

This system is based on creating an order through a closed system, current account tracking, based on current account or POS payment transactions, order tracking and order reporting based on the order. If desired, the order feature and price feature are hidden and open to the end user; different styles can also be designed.

System

Web-based B2U Objects platform Windows-based 2008R2+ servers and IIS

It works on 7.5+. It uses MS SQL Server 2012+ as database.

Settings

Its’ main parameters are defined under the general settings of the site. These are Site Name, e-mail recipients, erp information etc. are root informations. The site cache mechanism is cleared each time it is updated.

Definitions

Here is the information required for shopping on the site such as credit cards, banks, cargo information, etc. definable. Interventions require technical support.

Site General Management

Here, the static pages of the site (Contact etc.), product comments, Banner management, etc.

effecting parts.

Order Receiving Process

Ordering as a process, after logging into the system, the assigned products and their related based on price/discount, browsing between, adding to the order list, finalizing the order consists of steps. The order process works with two different methods. In the first method, with the order basket logic an order list is created by browsing through the products and adding the desired product to the basket. The second method; search for a product in a pop-up window on a single order list screen and add it to the list.

At the end of the order, according to the preferences, the delivery address, payment/purchase as deduction to the current account and e- order is created with the contract approval, the order process is completed.

Salesperson Transactions

By logging into the system on behalf of the current customers paired with them from the Salesperson Management panel. Salesperson can prepare orders on behalf of the customer, approves/rejects orders pending approval, if any, assigned to it during the approval process.

Customer Transactions

There can be multiple users for each client. Each user's order works under their own name, but in current reports, it follows its' own concierge in order tracking.

After entering the system, it prepares an order with the new list, if there is no old order list. From Excel loading bulk order is available.

Approves/rejects orders pending approval assigned to it during the approval process.

It monitors the current statement, order status report and item-based order report.

If it is needed, it makes POS payments based on the current account.

Salesperson-Customer Matching

Salespeople defined on the "Internal Users" screen in the system can be quickly accessed from the relevant screen. You can assign customers. In this way, the salesperson can write the order on behalf of the customer. Afterwards, customer approval or manager approval can be activated according to preference.

Organization Hierarchy

You can establish a hierarchical approval mechanism by defining more than one organization.

For example, hierarchy in the number of levels you want under the main group such as Domestic and International you can create. On the front, the approval mechanism is adapted according to this structure.

Users

There are 3 types of users in the system

1. Admin users; has the authority to manage the system. Operation in the entire Admin Panel, they can screen and make authorization-based.

2. Internal Users; Used for placards and their superiors. If necessary, requested in the Administration Panel access to screens can also be opened, for example, the interior you want to manage product images, you can give this permission to the user.

3. External Users (Members); are customer users that provide external access. Also these split in two;

   a. B2C: Retail buyers. In this open system, you can become a member yourself for systems.

   b. B2B: Your B2B customer's account paired with a specific customer (Current) account.

Users are managed by role or individual based authorization.

Product categories

It has a category level in the B2U Object Tree Structure as standard. But ERP you can also use it differently with adaptations according to the structure in your system, for example level like contraction. Under normal conditions; you assign the products to the categories prepared in the tree structure. Each product is in one or more categories. Ease of these searches and listings will provide.

Products

The product structure is very detailed. It can be defined directly in the system as well as various from ERP. You can pull in methods. One main thumbnail and as many details as desired on the products picture can be added. You can also find detailed information about the products.

ERP Integration (Netsis)

B2B platform; periodically pulls the following data from Netsis to its own database:

  • Exchange Rates
  • Product Categorization
  • Products
  • Order Status

The flow towards Netsis is in the form of sending an order record to Netsis at the end of the order. This confirmation It can be configured as post-approval or pre- and post-approval with the mechanism.