We have a UK customer with a live Pegasus Opera I accounts system.
They have hired us to setup a new osCommerce ecommerce web site - this is a separate project. There are issues such as different prices/discounts for different customers.
Pegasus Opera I is written in FoxPro DOS, source code not available, runs on FoxPro database.
We need to create a batch mode interface program that will manage Customers, Products, Orders and Receipts between the two systems - this requires two-way synchronisation.
To run on a PC at the office with ODBC connection to osCommerce MySQL database and LAN connection to server where Opera I FoxPro database is.
Don't mind what language the interface program is written in - we will own copyright in the code and you wil provide full compilable source code.
The program will write detailed logs for all activities
Customer
New customer is added to osCommerce - insert into Opera
Customer details are changed in Opera - update osCommerce
Customer details are changed in osCommerce - update Opera
There will be offline customers in Opera that are not linked to an osCommerce customer
Product
Initial one-time upload of Opera Products into osCommerce when system is first installed
New Product is added to Opera - insert into osCommerce
New Product is added to osCommerce - insert into Opera
Product details are changed in Opera - update osCommerce
Product details are changed in osCommerce - update Opera
There will be offline Products in Opera that are not linked to an osCommerce Product
Orders
Orders can have multiple lines
New Order is added to osCommerce - insert into Opera
Inserting an order into Opera may require creating an inventory allocation and diowndating available inventory
Inserting an order into Opera may require downdating a Customer's available Credit limit
Order details are changed in Opera - update osCommerce
Order details cannot be changed in osCommerce after Order is placed
There will be offline Orders in Opera that are not linked to an osCommerce Order
Receipts
New Receipt is added to osCommerce - insert into Opera
Inserting a receipt into Opera may require downdating a Customer's Account balance and available Credit limit
There will be offline Receipts in Opera that are not linked to an osCommerce Order
It will be an advantage if:
You know the osCommerce database structure
You have experience of synchronising osCommerce with a back office order processing/stock control./accounting system
You know the Pegasus Opera I database structure
This project is No. 1 of 4 projects we have for the same customer - each one is a separate Scriptlance project - other projects are :
2a) Quotation/Estimate system to run disconnected from Opera with ability to create XML Sales orders files
2b) XML Sales orders import ttol - import XML Sales orders files and push into Opera
3) Sales Returns system to link with Opera tables - create and process RMAs and insert Sales credit notes into Opera
4) Sales statistics reports - Customer has been re-keying Opera reports into existing Excel spreadsheets - replace keying-in with program reading data from Opera