Quoting Wil Cooley ([EMAIL PROTECTED]):
> On Tue, 2002-10-29 at 04:42, Peter Dabrowski wrote:
> >
> > E-commerce package in Perl, Allcommerce looks like going to be reborn again.
> > It contain Warhouse Management System to. Would be naice to port SL to it.
> > I offered them to do Polish translation.
>
> At some point there was talk of integrating SL with Interchange
> (http://interchage.redhat.com); does anyone know what became of that?
I did quite a bit with it -- I append the list of items proposed
and their status.
Basically, you can do all of:
-- Create new customer
-- Update customer via web
-- Place sales order
-- Place sales order with invoice
-- Place sales order with invoice and payment
-- Sync product database and inventory with SQL-Ledger; IC
items can be automatically added into SQL-Ledger
as they are ordered
Of course, given access to SQL-Ledger's Postgres tables, IC can do
just about any type of querying needed.
The addition was done by overriding the Form and User objects and
triggering the routines just as if IC was the CGI script.
It is the type of thing that the faint of heart would not install
yet, but that I (or any other competent IC consultant) could get
going pretty well in a matter of a few hours.
Best,
Mike Heins
Accounting
----------
* Vend::Accounting module added, along with example module for SQL_Ledger.
This is the basis for a start of a defined accounting system interface.
Some intended functions:
NOTE: AS = Accounting Software, i.e. SQL-Ledger, IC = Interchange
1. Assign customer number -- DONE
2. Change customer information based on input, limit to fields customer
should have control over -- DONE
3. Add sales transaction (IC) -- DONE
4. Feed back sales transaction from AS side for account status -- TODO
5. Enter payments (IC --> AS), with credit-cards used to pay invoices -- DONE
6. Reconcile AS account status with IC, i.e. ship status -- TODO
7. Cancel order (IC) -- TODO
8. Ship portion or all of order (IC) -- DONE
9. Mark order complete -- DONE
Input on other functions needed is appreciated.
PROPOSED:
* Set of modules selectable by route handle:
Vend::Account::SQL_Ledger (exists) DONE
Vend::Account::QuickBooks (proposed)
Vend::Account::Compiere (proposed)
Vend::Account::[fill-in-the-blank]
* Use a usertag [account] (a la [charge]) to interface functions. -- DONE
* Use a profile primitive, "&account=label function" ala "&charge="
to do some accounting functions in profiles, notably getting an
order number or customer number -- DONE
* Allow either COMMIT or no-COMMIT operation, with tradeoffs -- DONE
* Define accounting system parameters via Route, and build
in accounting functions into Route so that they can be
a predicate for order success. -- DONE (with Accounting Directive)
* Define two transitional state tables for handshaking: -- TODO
orderstatus -- status of orders, i.e.
pending,transmitted,received,shipped,complete
accountstatus -- record of payments and orders for account statement
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.513.523.7621 <[EMAIL PROTECTED]>
"Even if you're on the right track, you'll get run over if you just
sit there." -- Will Rogers
