In Suse start and stop order of services are managed by insserv package and based on dependency with other services. So it is little different. The answer to your question is given in details with examples in the following Suse article:
Manipulating the start and stop order of Linux services
Under the LSB (Linux Standards Base), the start and stop order of
services is controlled using the "insserv" package. Unlike Netware,
DOS and other operating systems, SUSE calculates the start and stop
orders based on dependencies. This idiosyncrasy of Linux has the
distinct advantage of providing a faster boot time, but does make
things a little more complex.
Here are few examples of how to manipulate the header of a service
defined in /etc/init.d.
The following example will start Service "myService" after the network
has loaded and will automatically start the service "myOtherService"
### BEGIN INIT INFO
# Provides: myService
# Required-Start: $network
# Should-Start: myOtherService
# Default-Start: 2 3 5
# Description: Example Service
### END INIT INFO